-
Notifications
You must be signed in to change notification settings - Fork 30.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Show checkmarks in top level menu to indicate activity of a toggle #14986
Comments
I like this idea since for consistency. fyi @bpasero |
The only reason our menu is not more dynamic is because it lives on the main side whereas many of the commands execute on the renderer side and thus would need to send back to the main side that the state changed. Not an easy area for a PR I fear. |
Verified that the checks show up when toggled, also found a bug with toggling word wrap (filed #62307) |
Actually, I've found inconsistent behavior with all of the toggle items under Appearance, the items do trigger but there is no checkmark when toggled. Re-opening. |
Some UX feedback (@misolori): I think we should not mix "Toggle..." and showing a checkmark. Either it should read e.g. "Sidebar" or "Word Wrap" having a checkmark or not or we should not show a checkmark and it should be "Show Sidebar"/"Hide Sidebar" or "Enable Word Wrap"/"Disable Word Wrap". Given my example we can also decide case by case. E.g. I find "Show/Hide Sidebar" easy to understand but for "Word Wrap" I can see us using a checkmark similar to "Auto Save". @sbatten we should probably make a pass over all our "Toggle..." in the menu and decide case by case, e.g. I see "Toggle Minimap" with a checkmark which is weird too. |
-- Sorry for the English, I used Google Translator --
Place a check in some menu to see if it is active or not. Similar to the Auto Save File> Auto Save
Mainly for options that do not change the text in the menu.
Example: Toggle Word Wrap, Toggle Render WhiteSpace, Toggle Full Screen, Toggle Developer Tools, among others.
The text was updated successfully, but these errors were encountered: