kicad-developers team mailing list archive
-
kicad-developers team
-
Mailing list archive
-
Message #30088
Re: GAL canvas behavior.
I think the object should remain selected after the context menu is closed.
But, right clicking on a *different* object should deselect the first one,
select the new one, and then open the context menu on the newly selected
item.
There are many times that erroneously deselecting the first item would
result in more work for the user, as they wanted to cancel the menu but not
the selection.
On 21 Jul 2017 03:22, "Wayne Stambaugh" <stambaughw@xxxxxxxxx> wrote:
> I've finally forced myself to start using the GAL canvas for new
> projects and I immediately ran into an unexpected behavior regarding
> context menus. If I right click on an object, it gets selected and the
> context menu for that object is shown as expected. If I change my mind
> and close the context menu with the escape key, the context menu
> disappears. So far so good but here is where things get ugly. The
> object from the canceled context menu is still selected so if I move the
> cursor to a different object and right click, the context menu from the
> previously (still) selected object appears and selecting a command from
> the context menu will be performed on the object at the first right
> click position rather than the object the cursor is currently over.
> This seems broken to me. I have to hit the escape key a second time to
> deselect the initial object selection. Is this the behavior we really
> want? I would expect that the initial object would have been deselected
> when I aborted the context menu (or performed a command on the selected
> object) so the next right click would select the new object. With the
> current behavior, I have to hit the escape key a second time to deselect
> the original selection. Anyone who has been following the dev mailing
> list for any amount of time knows how much I dislike additional steps to
> accomplish a task. This falls under that category in a big way. Can
> this be changed to mimic the behavior of the legacy canvas? If so, I
> will file a bug report. If not, we need to discuss this before I am
> willing to kick the legacy canvas to the curb.
>
> Cheers,
>
> Wayne
>
> _______________________________________________
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help : https://help.launchpad.net/ListHelp
>
Follow ups
References