Mail Archives: geda-user/2021/07/07/11:37:26
Roland Lutz <rlutz AT hedmen DOT org> writes:
>> The selection remained with the originally selected part(s) after
>> the copy and the new copy was not selected. The new gschem transfers
>> the selection to the copy when it is placed.
>
> I changed it this way because it's how most programs behave these days:
It use to be that the copy was selected. That was convenient, when
multiple copies are needed, just continue typing 'c' and move on.
Then it was changed, so that the original stays selected. That drove me
crazy, especially when I wanted to rotate the copy 'er', and the original
teleported into the nirvana instead.
Now I hear it was changed again?
Maybe it is time for a user preference?
>> http://git.geda-project.org/geda-gaf/commit/?id=c1d796ce
>
> You can undo this by going to line 148 of gschem/src/x_event.c:
>
> case (PASTEMODE) : o_place_end(w_current, w_x, w_y, FALSE, TRUE,
>
> and replacing TRUE with FALSE:
>
> case (PASTEMODE) : o_place_end(w_current, w_x, w_y, FALSE, FALSE,
>
> Just out of curiosity: how does your workflow look like, so you prefer
> the copied object to stay selected?
--
Stephan
- Raw text -