|SWT_AWT bridge [message #755320]
||Tue, 08 November 2011 06:16
| Greg B
Registered: November 2011
Our RCP application has Swing embedded within some SWT views using the SWT_AWT bridge.|
Jubula currently appears to have difficulties interacting with any of the embedded Swing components, a couple of examples given below:
- The Observation Mode tool does not appear to register any events within the Swing components. You can click and manipulate the Swing controls and the Observation Mode collects nothing.
- The Object Mapping Mode tool does not appear to be able to collect any of the Swing components. You can only seem to collect the SWT container that contains the SWT_AWT bridge.
- I tried using unbound_modules_concrete[5.2]/Actions (basic)/Click/ub_grc_clickInComponent[NUMBER_OF_CLICKS] to send mouse clicks to an embedded Swing component, but during execution this gave rise to an Action Error "Timeout received before confirming the posted event".
I have had success using unbound_modules_concrete[5.2]/Actions (basic)/Click/ub_app_clickInActiveWindow[NUMBER_OF_CLICKS; MOUSE_BUTTON; X_POSITION; X_UNITS; Y_POSITION; Y_UNITS] however I would only want to employ that level of interaction as a last resort!
I'm not at all surprised the SWT_AWT bridge causes such problems. Does anyone else have any experience of these issues or suggestions for workarounds?
The Swing content of the SWT_AWT bridge is essentially a Java Applet.
One workaround I'm considering is to add a main() to each embedded Swing container with a mechanism for populating the data model via command-line arguments. These components can then be launched and tested as individual Swing AUTs.
Powered by FUDForum
. Page generated in 0.01571 seconds