Implementing Hidden Menu State #122
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Introduces the 'hidden' menu state.
'hidden' State: In this state, the menu is completely hidden from the user interface, but the keybindings remain active. This allows users to continue using the keybindings without the menu being visible.
I changed the old 'hidden' to 'basic' to better describe it.
The primary motivation for these changes is to enhance the GUI export functionality.
Users can now use GUI export without the menu being displayed, a lot of users like to make cards with target words and sentences and some users may prefer to hide the menu to reduce visual clutter.