| Summary: | Seeing extra "Input Methods" as menu option. | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Pushkar Chawda <pushkar.c> | ||||
| Component: | SWT | Assignee: | Platform-SWT-Inbox <platform-swt-inbox> | ||||
| Status: | CLOSED DUPLICATE | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | ericwill, pushkar.c, Vikas.Chandra | ||||
| Version: | 4.11 | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Pushkar Chawda
Found this while searching https://stackoverflow.com/questions/56286410/how-to-remove-the-input-methods-menu-from-my-context-menu/56334213 I have already tried the below suggestion, used setData by getting default display, added the code in our main activator class construstor.
Display.getDefault().setData("org.eclipse.swt.internal.gtk.noInputMethod",true);
This was not working for me, not sure i am doing something wrong.
anyone who can help me with this.. Eric, can you share some light here? Please try with 4.13, I removed this menu entirely from SWT in either 4.12 or 4.13 (can't remember exactly which one). Yes, issue seems to be fixed in 4.13, do we have any way to hide/remove from 4.12 as well, as we are planning to support till 4.12 and we have tested our plugin till this version only right now. (In reply to Pushkar Chawda from comment #6) > Yes, issue seems to be fixed in 4.13, do we have any way to hide/remove from > 4.12 as well, as we are planning to support till 4.12 and we have tested our > plugin till this version only right now. No, sadly it's an internal thing. Is it critical? It is, as it gives additional option to user which we don't control and some option is not doing anything observable but some gives error, seeing which user may get suprised and open a issue with us. Sadly this issue is present in 4.11 and 4.12 version. hence i was looking a way to hide or handle this :( There isn't really much I can do as we don't backport fixes for older releases, now that we have the faster release cycle. I would advise to upgrade 4.13 as soon as possible. *** This bug has been marked as a duplicate of bug 548628 *** |