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
... and I am feeling really dumb for not beeing able to find the responsible code.
Branch: dotnet5
OS: Win11
Current behavior: Options dialog opens on key down F4 (and CTRL+ALT+SHIFT+O of course)
Expected: Same behavior as the other F-Keys
Notes:
Stacktrace leads to MainWindow.g.i.cs (((System.Windows.Input.CommandBinding)(target)).Executed += new System.Windows.Input.ExecutedRoutedEventHandler(this.Properties_Executed);) which is on line 22 in MainWindow.xaml which is a command binding but does not contains anything near F4.
The text was updated successfully, but these errors were encountered:
(Fixed this on my fork at DavidRieman@82faf40. Well, at least mostly - I blocked F4 key so it doesn't make shapes but also doesn't open the options dialog on recent versions of Windows. I think they auto-map F4 to the Properties command.)
... and I am feeling really dumb for not beeing able to find the responsible code.
Branch: dotnet5
OS: Win11
Current behavior: Options dialog opens on key down
F4
(andCTRL+ALT+SHIFT+O
of course)Expected: Same behavior as the other F-Keys
Notes:
Stacktrace leads to
MainWindow.g.i.cs
(((System.Windows.Input.CommandBinding)(target)).Executed += new System.Windows.Input.ExecutedRoutedEventHandler(this.Properties_Executed);
) which is on line 22 inMainWindow.xaml
which is a command binding but does not contains anything nearF4
.The text was updated successfully, but these errors were encountered: