I pushed the patch, as for now it has only received positive feedback. Perhaps after merging it will get more attention.
Cheers, Orson On 07/31/2017 06:58 PM, Wayne Stambaugh wrote: > Orson, > > I like this is behavior lot better. The hotkey behavior is much closer > to the legacy canvas. You may want to wait for feedback from the folks > who prefer to select everything. > > Thanks, > > Wayne > > On 7/31/2017 4:48 AM, Maciej Sumiński wrote: >> I think I got the right solution that would work for everyone. In case >> there was nothing selected before a right click, then the selection >> should be cleared after the context menu is shown (no matter whether >> cancelled or used). >> It is coherent with the hot keys behavior and allows the user to apply >> both working methods: either select items and decide on action or >> execute an action for a pointed item. I attach the patch for comments. >> >> Cheers, >> Orson >> >> On 07/20/2017 07:22 PM, Wayne Stambaugh 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@lists.launchpad.net >>> Unsubscribe : https://launchpad.net/~kicad-developers >>> More help : https://help.launchpad.net/ListHelp >>> >> >> >> >> _______________________________________________ >> Mailing list: https://launchpad.net/~kicad-developers >> Post to : kicad-developers@lists.launchpad.net >> Unsubscribe : https://launchpad.net/~kicad-developers >> More help : https://help.launchpad.net/ListHelp >> > > _______________________________________________ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp >
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
