We have a case where a Swing App is integrated within a RCP App and we need to switch between the two all the time.
Now, we managed to handle that using the _1 mechanism but this works only when we launch the Swing AUT that then launches the RCP AUT (when in fact the RCP one launches the swing one). So the _1 app is the RCP one.
So far so good, but now we can't type anything into the RCP app, we keep getting "Unsupported keyboard layout" problems. I assume this is related to the fact that the RCP app is launched through the Swing one that has no keyboard layout.
We first thought this was related to our French environment but when launching the RCP directly without the Swing one, we don't have any problems even when using a french keyboard layout.
We also tried to have the RCP launching the Swing one but we didn't manage to make it work.
The RCP application will be using the keyboard layout of the system. From our FAQS:
When you are testing SWT and RCP applications, you'll need to specify a keyboard layout in the AUT configuration. This tells GUIdancer or Jubula what layout your system is using. Note that the actual keyboard attached to the computer does not make a difference; the system regional settings are what counts.
If your keyboard layout for the system is French, I can imagine that this is causing the problem - at the moment, German and English are supported out of the box. In general, new keyboard layouts can be added, but there is a problem with French. As a workaround, you should set the keyboard layout on your test system to e.g. en_US.
For the moment we're only trying to write basic letters.
The strange thing is: when the RCP app is launched alone without the Swing one, then we can write using the french keyboard layout that we added (we didn't handle the special characters or numbers for the moment as we don't really need them yet) or using the en_US layout provided even when our system is French.
That's what made us think our issue is related to the launch through the Swing app.