-
Bug
-
Resolution: Unresolved
-
P4
-
1.4.2, 5.0, 9, 11, 12, 13, 14, 15, 16, 17, 18, 19, 21
-
Fix Understood
-
x86, sparc
-
linux, solaris_8
This is basically a SWT-AWT/swing interoperatibility issue.
It might not be possible to handle it now, unless SWT also implements some common protocol of interoperatibility, which is XEmbed in this case.
To reproduce this do the following:
i) Run the attached code.
It opens up a SWT Shell with SWT Components with a two AWT Components Embeded.
(U need to have swtlibraries in the CLASSPATH as well as swtnative libraries in the LD_LIBRARY_PATH. Also this code should be run with XAWT Switch only.
ii)Click the AWT Button 'AB', a modal dialog, "Test Dialog" opens up.
iii)Try to input any thing on the AWT Text Field as well as on the SWT Text Field, while u can't input anything on the AWT , u can do on the SWT Text Field.
As mentioned above, this might not be Bug on AWT, as SWT is still to implement the XEmbed Protocol.
It might not be possible to handle it now, unless SWT also implements some common protocol of interoperatibility, which is XEmbed in this case.
To reproduce this do the following:
i) Run the attached code.
It opens up a SWT Shell with SWT Components with a two AWT Components Embeded.
(U need to have swtlibraries in the CLASSPATH as well as swtnative libraries in the LD_LIBRARY_PATH. Also this code should be run with XAWT Switch only.
ii)Click the AWT Button 'AB', a modal dialog, "Test Dialog" opens up.
iii)Try to input any thing on the AWT Text Field as well as on the SWT Text Field, while u can't input anything on the AWT , u can do on the SWT Text Field.
As mentioned above, this might not be Bug on AWT, as SWT is still to implement the XEmbed Protocol.