You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Today, the way HotKey support works is the first view that added the key binding gets it's Command.Hotkey command invoked and then processing stops. This means if a layout has views with _Test, only the first will get focus when the user presses Alt-T.
It would be nicer if each press of the HotKey cycled between all the views in the visible hierarchy that have bound to that hotkey.
The text was updated successfully, but these errors were encountered:
That's a more natural and typical behavior for things like that.
If they are referenced in a central place, it can be done quite easily.
Since they're delegates, you can just "add" or "subtract" to the delegate (that's also why that works on events - it's exactly the same mechanism.
Doing that then means anything that has subscribed to the delegate will automatically receive the callback, and makes things like cancellation more natural to support, as well.
Today, the way HotKey support works is the first view that added the key binding gets it's
Command.Hotkey
command invoked and then processing stops. This means if a layout has views with_Test
, only the first will get focus when the user pressesAlt-T
.It would be nicer if each press of the HotKey cycled between all the views in the visible hierarchy that have bound to that hotkey.
The text was updated successfully, but these errors were encountered: