Bug 361353 - IME location
Summary: IME location
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 3.7.1   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform-SWT-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-19 04:33 EDT by Irina CLA
Modified: 2019-11-28 05:44 EST (History)
3 users (show)

See Also:


Attachments
screen capture (9.13 KB, image/png)
2011-10-20 05:42 EDT, Irina CLA
no flags Details
ImeSWTTest.java (1.87 KB, text/plain)
2011-10-20 05:49 EDT, Irina CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Irina CLA 2011-10-19 04:33:29 EDT
Build Identifier: swt-3.7.1

We have a touch SWT-GUI-application with a virtual keyboard integrated in the GUI. Our problem is, that the IME activated by StyledText we use for text entering overlaps the keyboard located below the StyledText. 
Is it possible, to keep the IME location within a defined client area?

Reproducible: Always

Steps to Reproduce:
1.Japanese IME in Win-XP
2.
3.
Comment 1 Felipe Heidrich CLA 2011-10-19 11:16:31 EDT
Can I see a screen capture ?

What happens If you replace StyledText by a Text ?

StyledText uses in-line input method, so I'm note sure how this overlapping is happening.
Comment 2 Irina CLA 2011-10-20 05:42:08 EDT
Created attachment 205600 [details]
screen capture
Comment 3 Irina CLA 2011-10-20 05:49:08 EDT
Created attachment 205602 [details]
ImeSWTTest.java

just a test application to visualize the problem.
Comment 4 Felipe Heidrich CLA 2011-10-20 10:03:16 EDT
(In reply to comment #1)
> What happens If you replace StyledText by a Text ?

Please try the suggestion above.

The window we see in the screenshot is the candidate list, it is alinged with the caret position and it shows on top of ther UI elements. Not sure how to fix this problem.
Comment 5 Irina CLA 2011-10-20 10:55:54 EDT
(In reply to comment #4)
> (In reply to comment #1)
> > What happens If you replace StyledText by a Text ?
> Please try the suggestion above.

I've tried it: There is no difference.
Comment 6 McKaot CLA 2011-11-15 05:21:00 EST
I had similar problems with japanese... so I just moved to a 3rd-party implementation. But @WINDOWS I think you cannot dictate the users the IME the have to use ;{

I guess it's kinda difficult to solve it in a general way because of all the different OSs.
On the other hand: it's "just" window handling, isn't it?
Comment 7 Remy Suen CLA 2011-11-15 08:16:42 EST
(In reply to comment #5)
> (In reply to comment #4)
> > (In reply to comment #1)
> > > What happens If you replace StyledText by a Text ?
> > Please try the suggestion above.
> 
> I've tried it: There is no difference.

No difference for me either when inserting Japanese on Windows 7.
Comment 8 Felipe Heidrich CLA 2011-11-15 16:18:58 EST
The candidate list window is placed by the IME program next to the caret.
I don't think we in SWT can control it.
Comment 9 Andre Saibel CLA 2012-01-11 04:39:30 EST
The requierement for nice (meant as "something like in iPhone") integrated touch uis seem to come in vogue. 

The previous posts suggest that with SWT it's not possible to implement such an integrated ui with a virtual keyboard placed near by the text input in an acceptable way without having to implement an own IME, too.

There are "agressive" IMEs (like the Japanese) and moderate ones, of course, but for all of them I lack a general way to (at least) determine the bounds of the IME window for the sake of beeing able to layout the underlying dialog. The even better way would be the possibility to "squeeze" it into own layout - I think this is not that simple to do. For me, the suggetion to restrict the area where the IME can be placed sounds sense. Is it technically feasible in any way?
Comment 10 Irina CLA 2012-03-07 13:18:38 EST
What is the status quo? Are there any solutions in sight?
Comment 11 Lars Vogel CLA 2019-11-14 03:26:13 EST
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

If the bug is still relevant, please remove the "stalebug" whiteboard tag.