Java Solaris Communities Sun Store Join SDN My Profile Why Join?
 
Bug Database
Bug Detail
Quick Lists
Top 25 Bugs
Top 25 RFE's
Recently Closed Bugs
Printable Page Printable Page


Bug Database
Bug ID: 4425917
Votes 0
Synopsis Merlin : Input method switching does not work well in Solaris and x86 solaris
Category java:classes_awt
Reported Against merlin-beta
Release Fixed
State 6-Fix Understood, bug
Priority: 4-Low
Related Bugs 6246541 , 4391718
Submit Date 15-MAR-2001
Description
  xxxxx@xxxxx   2001-03-15

java  version "1.4.0-beta"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.0-beta-b55)
Java HotSpot(TM) Client VM (build 1.4beta-B55, mixed mode)

locale : zh_CN
encoding : zh_CN.EUC and zh_CN.GBK

Input method switching does not work well in Solaris
and x86 solaris platforms. 

One of the IM, for example, Wubi IM is selected and the status
window appers, then, select another IM, for example, Test IM,
Test IM can not be selected and Wubi remains selected and available 
and Wubi status window is still displayed.

This bug doesn't appears in windows platform.
This bug doesn't appears in merlin b48.
This bug doesn't appears in ladybird b18.

This problem is very similar to Bug 4391718, which is filed for
ladybird b08.
  

To reproduce this problem,

1, Backup all files in $JAVAHOME/jre/lib/ext
2, tar xvf the attached file
3, Copy WuBi.jar to $JAVAHOME/jre/lib/ext
4, Compile all .java file.
5, Execute
     java SPI101 zh
   to come up with the Window for SPI101.
6. Click on the client component to give the input focus
7. Select "Select Input Method" from the system menu,
   and  choose WuBi input method 
8. Click on the client component to give the input focus.
    (the WuBi IM Status windows should be pop up)
9. Select "Select Input Method" from the system menu,
   and choose Test Input Method
10. Click on the client component to give the input focus.   
  
    The Test IM Status windows should be pop up.

---- end of   xxxxx@xxxxx   2001-03-15
Work Around
N/A
Evaluation
This problem is reproducible when the window manager's focus policy is "focus-follows-mouse" mode.

It seems that at the step 9, if the user moves the mouse pointer out of the client component to the System Menu Icon of the Motif Window Manager, the focus goes out of the client component right away.  This makes changing the input method inoperable, as the current focused input context is unknown for this component.  Interesting thing is that this behavior is not observed at the step 6.  This makes me think that this is likely to be an AWT focus problem.

  xxxxx@xxxxx   2001-03-19

Commit to fix in Merlin (regression).  
  xxxxx@xxxxx   2001-03-19

Most probably it is the same bug as 6246541. On CDE, I see not described in this bug behavior but immediate disappearance of Test IM window upon opening. Most probably, it is because of a focus problem and is WM-dependent.
  xxxxx@xxxxx   2005-05-31 13:29:04 GMT
Asked IM guys how important this bug for them.
Posted Date : 2005-09-27 11:19:15.0

According to IM guys, this input method is not important.  There seems to be a problem with opposites or their usage, however it doesn't manifest on usual scenarios.  Therefore, leaving it for Dolphin.
Posted Date : 2005-09-28 14:12:14.0
Comments
  
  Include a link with my name & email   


PLEASE NOTE: JDK6 is formerly known as Project Mustang