Community
Participate
Working Groups
20021218 It is not currently possible to get the IME anywhere in Eclipse in Linux GTK. STEPS 1) Change Locale to Simplified Chinese before logging in 2) Go to any application except Eclipse. 3) Hit Ctrl-Space. IME comes up. 4) Hit Ctrl-Space again. IME closes. 5) Start Eclipse 6) Go to a text file. Hit Ctrl-Space. Nothing happens.
Tod, I believe this is fixed. Can you get the latest and retest. Thanks.
I am still getting the problem in 20030122
Verified that this is true in the ControlExample. It seems that once the IME has been successfully invoked from a single-line native text widget (it won't come up in the native multi-line text widget either), then Ctrl+Space will bring it up in a StyledText. Several things to note: - Chinese GTK 2.006 is wildly unstable and GP's constantly - Chinese GTK 2.2.0 is more stable, doesn't GP and doesn't have the problem Sorry can't do anything other than suggest an upgrade to GTK 2.2.0.
*** Bug 30351 has been marked as a duplicate of this bug. ***
We still could't get SCH IME on StyledText with I20030129 build on RedHat8.0 with GTK+ 2.2.
Drat, wasn't fixed by GTK 2.2.
SSQ to investigate and advise.
Grant, Please talk to Silenio about this.
Felipe's back, so reassigning.
Run the ControlExample on the same system. (you can run it from inside eclipse if you wish). Go to the Text tab. You'll be able to enter chinese on both (in the native Text and also in the StyledText). In fact we can not enter chinese on the JavaEditor. The shortcut to turn the IME on conflits with the JavaEditor shortcut to the content assist (Ctrl+Space). The bug on SWT is: why the OS is not filtering the Ctrl+Space before it goes to the widget. I also tried to change the shortcut to the content assist in the preference page, for some reason (maybe Tod can say something here) it makes not difference.
I have just tried this in windows and I can do the keybinding and IME change there. I don't have a machine with Redhat 2.2 so we should look at this together.
Ok, I will have to move this but to UI. In GTK the event is filter after it be dispatch, SWT is correctly doing this on key up and key down. In this case the menu gets the event first, fire the accelerator (whitout filtering the event first), and then they eat the event (stop propaganting it). It all happens inside the GTK. There is not way to workaround this on SWT. UI team will really need to call removeAccelerator when a keybind is undefined.
Created attachment 3585 [details] Test Case This example show how to remove the accelerator (menuItem.setAccelerator (0)) and proves that doing this really fixes the problem.
Moving PR to key bindings owner. This one is very high priority for the East Asian test group so it is important that it gets sorted out.
Today I made the changes to ensure that for "zh" locales, etc., Ctrl+Space & Ctrl+Shift+Space are not registered as accelerators. It will be in tomorrow's integration build.
