X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com X-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to; bh=rBo2Yfmr/Lbuk7rmyA1cO98IiWDBquDpP3RRM3DDVRQ=; b=WdQBAlNXNuL99yAlF29MB5gJU+Jhvc+uO1Lf97F7V9YhJCKakjJkM1pxRxJYksa4Eg i7c3V4XI6niUSis6a0HfENL7vpGvSoktSTEQg/ybCoEXdE+beOSKsDPc7ttjsBmgm1fV lg4Ss5eOq6FQJQCfl6EwLSKO+tVE34sZaGPAmwLjDEUpRILKt2e9umJGiWlZxCvQYuQ9 a7MgDkp10OlhO/cwoXYfS264jKc9oTCo/ZPSo7buZ8GOScR2Ouehaw4KdLp4Hefw8aqn y1mKvwX5t67xhRqRzTeoJuGZHSBll2oYSHO8iJu2xLhCv3Z1xch+d902Rz7ICNCeIsWW XZVA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to; bh=rBo2Yfmr/Lbuk7rmyA1cO98IiWDBquDpP3RRM3DDVRQ=; b=S4GU+Bak13KqDP4VlCA/YzvQjwEsrxAsn8fII1u2zWvVvQX2HbvRD4Zgwn5n6hhcdr C3kggLfalItRHjVtfVuK8Xi26ttarpUc3JRe2BOfrPCuzCnb6cEmTfR3DzHmoj022GYA OPeG4KOVcQ04A0EpPWmgdCFS9CXDTcVcCHncOgvxZWve5cU94X+2ybPSBrWgDyUnQHdv JtWgBZSQOa634rW2niyg5TYzki1UZXmD5v3qzfFXy8Hy9u5JTnoWqC+l1NVINSwi+ZgB wRK1MCSD52ButVG+2IAl+VC7cBkRbdpcb/OS9cRAg2e8BRi7ZrKVJfhC8p610aWpiav8 cj1w== X-Gm-Message-State: AG10YOROVdadj+uDhuhCymUtmF1ZMqPfIvu2r7Tti51j21pvZqCAWK4zcuAbvYd4ywHtD34sR0cZn9EqesDWEw== MIME-Version: 1.0 X-Received: by 10.28.173.143 with SMTP id w137mr102419wme.101.1456425529252; Thu, 25 Feb 2016 10:38:49 -0800 (PST) In-Reply-To: <201602251657.u1PGvN4Z002963@envy.delorie.com> References: <201602242140 DOT u1OLe6e5023051 AT envy DOT delorie DOT com> <201602250326 DOT u1P3Q2bF003329 AT envy DOT delorie DOT com> <201602250358 DOT u1P3w5GD004211 AT envy DOT delorie DOT com> <201602251657 DOT u1PGvN4Z002963 AT envy DOT delorie DOT com> Date: Thu, 25 Feb 2016 09:38:49 -0900 Message-ID: Subject: Re: [geda-user] Import schematics doesn't fully honor Settings->Import New Elements At->Mark From: "Britton Kerin (britton DOT kerin AT gmail DOT com) [via geda-user AT delorie DOT com]" To: geda-user AT delorie DOT com Content-Type: text/plain; charset=UTF-8 Reply-To: geda-user AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: geda-user AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk On Thu, Feb 25, 2016 at 7:57 AM, DJ Delorie wrote: > >> It's not a big deal either way, it just looked like a reasonable >> option to simplify things. Is this the only way the mark function is >> overloaded, or are there others that you know of? > > It's also used when converting buffers to elements, and in general, > when dealing with buffers at all (although it's implicit). For me it looks like convert buffer to element uses the point that was clicked when the selection to be converted was cut or copied, the mark seems to be ignored. This is for sure another case where the click is significant and useful though. If there were some way for the UI to announce how it's going to interpret that click (eg new element centroid) or something. A lot of these things are minority operations and it may not be worth it though. > Elements also have a "mark" so think of the ctrl-M mark as "a mark" > instead of "the mark". Do these two different things that get referred to as mark have anything in common?