-
Notifications
You must be signed in to change notification settings - Fork 235
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
Modifier keys in menu items mistaken (Meta, Control) #117
Comments
I will be running some massive tests on Mac OS X soon and will try to fix all the issues I will find, including this one and other reported. |
I also notice that the default text actions have the wrong modifier |
It is related (partially), so one issue is fine :) This one is the components hotkeys mapping issue. Happened generally because basic look and feel (which is the base for WebLaF) has windows-like hotkeys and it seems that they do not properly change according to underlying OS. |
Btw, I will include this fix in v1.29 update. |
Is this fix still scheduled for 1.29? |
Yes, it is. All bugs which are set to v1.29 milestone will be fixed with v1.29 release. Most of features and enhancements which are set to v1.29 will also be included, but some of those might be re-scheduled for the next update depending on how this release goes. |
Bump.. a customer informed me about this bug today. Is there a patch that can be released for it? |
http://stackoverflow.com/questions/9780028/mac-keyboard-shortcuts-with-nimbus-laf - that solution worked for me as a workaround for each individual component that didn't work properly. |
I started to investigate this one and got kinda stuck. Unfortunately I'm not using mac a lot, so I'm not really sure how hotkeys should be handled there and which hotkeys for which application areas are better. I have asked a few colleagues who are using Mac OS X a lot and they said that Right now there is an old workaround in WebLaF code that always handles So I'd really like to hear your comments about how different hotkeys should be acting on Mac OS X in different application areas. That would help me to correctly adjust the hotkeys handling within the library and avoid similar mistakes in future. |
The two issues:
I think Nimbus works correctly so could serve as a template. |
Sounds reasonable, but the problem is - Nimbus uses the same keys basic L&F provides. Here is an example of how L&F keystrokes are defined: "TabbedPane.ancestorInputMap", new UIDefaults.LazyInputMap(new Object[] {
"ctrl PAGE_DOWN", "navigatePageDown",
"ctrl PAGE_UP", "navigatePageUp",
"ctrl UP", "requestFocus",
"ctrl KP_UP", "requestFocus",
}), This specific part is the same for both Nimbus and WebLaF and I couldn't find how exactly hotkeys like It seems that Unfortunately I can't really run any tests on Mac OS X right now - will get my hands on a macbook only tomorrow, so right now I can only ask: |
I'm also not on Mac now, but from the code you posted that definitely will not use |
I guess I will check this out tomorrow then, maybe there is something I have missed in the code, some tricky workaround somewhere - Swing is full of those.
The main question is whether I will have to do adjustments in L&F defaults or some tricky workarounds for specific components. I will need to test Nimbus first to see how it handles that stuff (if it does at all).
To be honest, I'd stick with |
I just noticed that when running an application under OS X, the menu item short cuts show wrong modifiers. For example, if a short cut is Meta + A, this is only shown as A. In turn, if I use Ctrl + A, this is shown as ⌘ + A (using the command symbol rendering for Meta.)
The text was updated successfully, but these errors were encountered: