-
Notifications
You must be signed in to change notification settings - Fork 2
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
Menus and submenus need enable property #85
Comments
I just pushed for this issue. The enabled property has now been implemented so that it doesn't
If so, it'll take 5 minutes to update this and I'll do a new push and close the issue. |
After talking with Steve, a new implementation has been added for having the enabled property be set |
The disabled menus need to have their appearance changed. The graying of the background makes it look like the menu is actually selected. A disabled menu should have the same background as normal, but the text should be greyed out, similar to the following from TSTool. The following also shows menu separators, which I mentioned in another issue. |
New changes were made and pushed. As of now the menus are appearing the correct way whether |
The latest push has
enabled
property on submenus. However, I did not have in myapp-config.json
file. The behavior in this case was that no submenus showed. Also, setting tofalse
does not seem to work. The behavior should be as follows:enabled
should default totrue
if not in the config filefalse
should still display the menu but it should be grayed out - this will allow new features to be laid out for demonstration purpose and functionality filled invisible
should be added with defaulttrue
andfalse
will not display the menu item at all - this is lower priorityThe text was updated successfully, but these errors were encountered: