Community
Participate
Working Groups
OS: Mac OS X 10.5.2 (intel) Build: Eclipse 3.4M6a The default key binding for launching Plugin Spy is Shift+Option+(Fn+)F1, but it didn't work. In addition, we cannot set this key binding in the Preference page by manual operation. If we assign another key binding for Plugin Spy, it really works, so please alter the default key binding.
Kim, is there something I don't understand about Mac's here?
Default behaviour on the Mac (laptops at least) is for the function keys to map to control functions such as brightness, volume, and expose. To use them as actual F keys you need to hold down the Fn key. You can swich this behaviour such that the Fn is the default, and in that scenario the keybindign works, but this bug is real. If you have your keyboard in the default mode Shift-Option-F1(fn) does not work. Interestingly enough, other Fn keys do work in this scenario...
I'm using Mac mini (intel) with a new aluminum keyboard (JIS). According to your suggestion, I changed the default behavior of Fn keys in the System Preference page. But Shift+Option+F1 (without Fn) didn't let Plugin Spy come up yet... I tried some keybindings as follows: Shift+Option+F1 - cannot set - dont work (by default) Shift+Option+\ - can set - works Shift+Control+F1 - can set - works Shift+Command+F1 - cannot set - (dont work) "can set"/"cannot set" means I could/could not overwrite keybinding for Plugin Spy on General > Keys in the Eclipse Preferences page.
Paul, do you know of keybindings that do this? ie., declare two, use that 'carbon' platform hack to accommodate Mac users?
(In reply to comment #4) > Paul, do you know of keybindings that do this? > Yes, there are a couple of key bindings that use something (like ALT+LEFT_ARROW on most platforms, M1+[ on carbon) You just need to pick a safe, logical key for the mac. Tadayuki, it sounds like some other program is eating the key on your mac. Kim, does the keybinding work on your Mac at all? PW
(In reply to comment #5) > (In reply to comment #4) > > Paul, do you know of keybindings that do this? > > > > Yes, there are a couple of key bindings that use something (like ALT+LEFT_ARROW > on most platforms, M1+[ on carbon) > > You just need to pick a safe, logical key for the mac. > > Tadayuki, it sounds like some other program is eating the key on your mac. > Kim, does the keybinding work on your Mac at all? > > PW > It works if I change the default Fn key behaviour in the System Properties first. If I have to use the fn key to get regular Fn behaviour I see the result as Tadayuki. Tadayuki, are you running in the English locale?
I have checked this problem both Japanese and English locale (note that I have v10.5 installed in Japanese) After searching several web pages regarding Kotoeri (Japanese IME on Mac), I got some findings as follows: 1. Kotoeri cannot be disabled when v10.5 installed in Japanese (grayout in input menu on the menu bar) 2. Kotoeri keeps traditional (Mac OS 9) keybindings for switching input modes among Hiragana, Katakana, and English (Romaji). For example, we can use traditional way of Option+Shift+F1 for switching to Hiragana as well as modern Ctrl+Shift+J (as yo can see in input menu) So... I believe Kotoeri would catch Option+Shift+F1 and similar keybindings as used in the earlier version of Mac OS for most (carbon-based?) applications Here are some typical keybindings caught by Kotoeri: traditional (modern) - mode Option+Shift+F1 (Ctrl+Shift+J) - Hiragana Option+Shift+F2 (Ctrl+Shift+K) - Katakana Option+Shift+F4 (Ctrl+Shift+;) - Romaji
(In reply to comment #7) > I have checked this problem both Japanese and English locale (note that I have > v10.5 installed in Japanese) > > After searching several web pages regarding Kotoeri (Japanese IME on Mac), I > got some findings as follows: > > 1. Kotoeri cannot be disabled when v10.5 installed in Japanese (grayout in > input menu on the menu bar) Thank you, that helps. Chris, you would want to redefine the keybinding for plugin spy for carbon (or don't specify carbon if it is an IME problem that is not platform specific) and their locale. For example (from org.eclipse.ui/plugin.xml): <!-- Special content assist key bindings for the Chinese language to prevent conflict with IME --> <key locale="zh" contextId="org.eclipse.ui.contexts.dialogAndWindow" schemeId="org.eclipse.ui.defaultAcceleratorConfiguration" sequence="CTRL+SPACE"/> <key locale="zh" commandId="org.eclipse.ui.edit.text.contentAssist.proposals" contextId="org.eclipse.ui.contexts.dialogAndWindow" schemeId="org.eclipse.ui.defaultAcceleratorConfiguration" sequence="M3+/"/> PW
mine
Created attachment 97402 [details] org.eclipse.pde.runtime.patch I've decided to use M1+M3+F1 That looks like it should work. Can you please verify Yoshida? I have no Mac to test :/ >20080424
Created attachment 97403 [details] mylyn/context/zip
done!
Chris, you need this line as well: <key contextId="org.eclipse.ui.contexts.dialogAndWindow" platform="carbon" schemeId="org.eclipse.ui.defaultAcceleratorConfiguration" sequence="M3+M2+F1"> </key> That "deletes" the original binding for carbon. Although I'll point out that you have changed this key for all mac users. The other way would have been: <key contextId="org.eclipse.ui.contexts.dialogAndWindow" locale="ja" schemeId="org.eclipse.ui.defaultAcceleratorConfiguration" sequence="M3+M2+F1"> </key> <key commandId="org.eclipse.pde.runtime.spy.commands.spyCommand" contextId="org.eclipse.ui.contexts.dialogAndWindow" locale="ja" schemeId="org.eclipse.ui.defaultAcceleratorConfiguration" sequence="M1+M3+F1"> </key> This fixes the problem for the japanese locales. PW
Thanks Paul, I updated it to the latter scenario to not piss off the other Mac users. Please verify this Yoshida when you have time :)
Hi, Since the latest version of plugin.xml (v1.47) is not incorporated in the build as of Apr 28, I inserted the modified lines to plugin.xml (extracted from org.eclipse.pde.runtime_3.4.0.v20080324-0900.jar) manually, then clean up the workbench. When running in "ja" locale, the new keybinding (Option+Command+F1) for Plugin spy is successfully shown in the Preference (and verified unchanged in "en" locale), but it still won't work. Plug-in spy window didn't show up yet. This sequence must be trapped by another application on Mac v10.5.2 Japanese as found by the fact that I cannot set this sequence for Plugin spy in the Preference page. Please note that sequence of Control+{Shift or Option or Command}+F1 does work for my environment.
This bug doesn't fix Ganymede Stable Release(it doesn't MILESTONE RELEASE!) on Windows and Japanese Locale Environment. Please re-open this BUG!!!(Because Plug-in Spy is good feature for plug-in developpers!) I think these code are needed for Mac OSX <key contextId="org.eclipse.ui.contexts.dialogAndWindow" locale="ja" schemeId="org.eclipse.ui.defaultAcceleratorConfiguration" sequence="M3+M2+F1"> </key> <key commandId="org.eclipse.pde.runtime.spy.commands.spyCommand" contextId="org.eclipse.ui.contexts.dialogAndWindow" locale="ja" schemeId="org.eclipse.ui.defaultAcceleratorConfiguration" sequence="M1+M3+F1"> </key> I read the help about org.eclipse.ui.bindings.The "M1" is only supported for Mac OSX.So the other OS's Eclipse Japanese users can't use this sequence. I attached this patch is tested on Windows and Japanese Locale Environment.
Created attachment 107799 [details] for Windows and Japanese Locale user's patch
reopening due to japanese issue
targetting for 3.4.1
Thanks, fixed in 3.5 and 3.4.1
in helios,is the key binding changed? My development environment has same problem on Mac OSX and Japanese locale Environment. The plug-in selection spy's key binding is "Command+Option+F1".It is shown on preference. I changed to �hOption+Shift+(fn)+F1�h(F1 is hotkey of darker screen. So I pressed "fn" key.But if it is pressed fn and option, os handles "Alt" key...) and tested.It is executed. Plug-in menu spy's key binding is "Option+Shift+(fn)+F2". So it should has similar binding. Please reopen this bug...
On Mac OS X, the default shortcut key for Plug-in SPY is set to command+option+F1. However this doesn't work.
this comes to work if you change the shortcut key to other one, for example option+Shift+F1 which is the similar shortcut key as other platforms. I tried making the changes back to the default (command+option+F1), I couldn't set it because "F1" is not displayed on the field when I click both command and option keys together. Please reopen this bug and assign another shortcut key. Thanks.
