X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
X-Injected-Via-Gmane: http://gmane.org/
To: geda-user AT delorie DOT com
From: Kai-Martin Knaak <kmk AT familieknaak DOT de>
Subject: Re: [geda-user] how to fix cut and copy behavior when no selection
Date: Sun, 28 Feb 2016 15:47:10 +0100
Lines: 43
Message-ID: <nav19e$oks$1@ger.gmane.org>
References: <CAC4O8c8Syp2o8AZ45OW+1G=L550v_rXpymxy3gdSa+PXBGGBvw AT mail DOT gmail DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7Bit
X-Complaints-To: usenet AT ger DOT gmane DOT org
X-Gmane-NNTP-Posting-Host: a89-182-43-9.net-htp.de
User-Agent: KNode/4.14.10
Reply-To: geda-user AT delorie DOT com

Britton Kerin wrote:

> Without a selection:
>           * hot keys (Ctrl-X Ctrl-V) dump you in paste mode with
>             nothing to paste and the crosshair locked in a strange
>             way
>           * menu items put in expect-click mode, but when they get 
>             a click they don't actually cut or copy anything, but
>             instead lock the crosshair in a strange way and dump you
>             in paste mode, only with nothing to paste

I agree, this is an issue which irritated about every student I 
introduced to geda. 


> Options:
> 
> 1. Require a selection, give an erro pop-up if there isn't one.
> * Pros: simplest to implement, minimal surprise, surprise explained
> * Cons: requires a selection
> 
> 2. If no selection, overload hovered/clicked point to select
> object in addition
> to establishing snap point.
> * Pros: single-element cut/copy behave as probably expected,
> more convenient for experienced users also
> * Cons: slightly harder to implement, potentially surprising
> behavior
> 
> Opinions or other approaches?

I like the second option. It is compatible with the general notion: 
"use selection if it exists, else use the object under the mouse 
pointer". IMHO, the ability to act on objects without explicit 
selection is one of the strengths of the current pcb GUI. 

There is one item on my wish list, that would make this paradigm much 
more transparent --> Somehow highlight the object under the mouse so 
you can see in advance what is going to be affected by an action. The 
challenge is to find a non-obtrusive way that "works" even in crowded 
circumstances.

---<)kaimartin(>---