Community
Participate
Working Groups
When using External Key Combination with an RCP AUT, certain base keys are not being recognized / handled correctly. When e. g. using "COMMA" as a base key and shift as modifier, a capital "C" is being output instead of a semicolon ";" (at least that's what should happen when using the german keyboard layout).
Actually, this problem only occurs when using Key Combination. External Key Combination on the other hand behaves correctly. Since using External Key Combination is a workaround for this bug, I will no longer work on this for now.
I think the fact that SWT / RCP is not working is more a lacking feature than a bug (this is also mentioned in the manual, though I think a bit incorrectly: https://testing.bredex.de/files/content/software/documentation/reference/actions/ch05s01s02s01.html ) The main reason I think is that the SWT class contains the key codes only for the non-typeable keys (e.g. F1 - F12, etc), and we create the SWT Key Events using these codes. Probably we could do something similar for the other keys, but I'm not sure that would really worth the huge amount of work now. In general, External Key Combination / External Input Text should work (corresponding methods: AbstractApplicationTester.rcNativeKeystroke / InputText). These actions use the AWT Robot to generate AWT Events and execute the keypresses / releases. The 'internal' actions use the toolkit-specific robots to generate toolkit-specific events. I think one should use the External actions except if it is important to generate the toolkit-specific events. There's also another twist to the story, because the (External) Input Text actions sometimes accept non-alphanumeric characters, and sometimes don't... I'm going to set the ticket Wontfix now, because I think improving the keytyping code would require considerable effort, and since the External actions seem to be working for most cases.
