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
Instructions: Delete text to unset. Press Return key to accept. Focus out to ignore. Resets to previous value when invalid.
I find that this only works if the text field is non-empty. If the field is empty, after pressing Return and close the setting menu, the shortcut is reset to previous value.
Speculations: Perhaps the delete text to unset part of the logic is not working? Or the press Return key event is only triggered when the field is non-empty? Or empty text is considered invalid so the resets to previous value when invalid rule is invoked?
This is particularly frustrating because the program makes no indications that you have not successfully disable the shortcuts. Instead, it looks as if the shortcuts are unset, but they're actually not, and you only find that out when you try using them or close the setting menu and open it again.
screen.recording.mp4
I suggest until you can fix this bug (or better yet, implement #234), perhaps you could let the fields display their current registered values immediately after they are out of focus, so that the user immediately knows if their modifications fail.
The text was updated successfully, but these errors were encountered:
Instructions:
Delete text to unset. Press Return key to accept. Focus out to ignore. Resets to previous value when invalid.
I find that this only works if the text field is non-empty. If the field is empty, after pressing Return and close the setting menu, the shortcut is reset to previous value.
Speculations: Perhaps the
delete text to unset
part of the logic is not working? Or thepress Return key
event is only triggered when the field is non-empty? Or empty text is considered invalid so theresets to previous value when invalid
rule is invoked?This is particularly frustrating because the program makes no indications that you have not successfully disable the shortcuts. Instead, it looks as if the shortcuts are unset, but they're actually not, and you only find that out when you try using them or close the setting menu and open it again.
screen.recording.mp4
I suggest until you can fix this bug (or better yet, implement #234), perhaps you could let the fields display their current registered values immediately after they are out of focus, so that the user immediately knows if their modifications fail.
The text was updated successfully, but these errors were encountered: