SikuliX

Some combinations with shift key won't work

Asked by sathya

I am trying to select some list in a drag down box where i need to use "ctrl+shift+end" or "shift+end" to select all devices.
I've tried using
"type (Key.END, KeyModifier.SHIFT | KEY_CTRL )"
"type(Key.END,KeyModifier.SHIFT)"

But these won't work for me..I can use shift+pagedown for selection but that wont work as well.

Is there anyother way i can do this ?
Thanks in advance.

Cheers :)
Sathya

Question information

Language:
English Edit question
Status:
Solved
For:
SikuliX Edit question
Assignee:
No assignee Edit question
Solved by:
RaiMan
Solved:
Last query:
Last reply:
Revision history for this message
RaiMan (raimund-hocke) said : 		#1

sure, that the drop down has the correct focus at this moment?
if yes, put in a short wait(0.5) or so, before issuing the type.

ctrl+shift+end is type(Key.END, KeyModifier.CTRL + KeyModifier.SHIFT)

Revision history for this message
sathya (bksathyamoorthy) said : 		#2

@Raimund

Yes the drop down is in focus and I've put a wait after that too.
When i do it manually ctrl+shift+end works to select list in the menu but sikuli won't do it.

            click(Pattern("messaging_selectdevices.JPG").targetOffset(-1,3))
            wait(1)
            type(Key.END, KeyModifier.CTRL + KeyModifier.SHIFT)

Sikuli scrolls the drop menu to the end but doesn't select the list.

Cheers :)
Sathya

Revision history for this message
Best RaiMan (raimund-hocke) said : 		#3

if it is on Windows, there is some problem with the Num-Lock switch.

check bug 894312

Revision history for this message
sathya (bksathyamoorthy) said : 		#4

@Raimund:

Ah!! this explains it.
Thanks a lot. That solved my problem.

Hope this will be fixed in the upcoming version :)

Cheers,
Sathya

Revision history for this message
sathya (bksathyamoorthy) said : 		#5

Question resolved.

Revision history for this message
sathya (bksathyamoorthy) said : 		#6

Thanks RaiMan, that solved my question.

Revision history for this message
RaiMan (raimund-hocke) said : 		#7

I am sorry, but surely not fixed with 1.1.0.

But I have put it high prio for the 1.2.0 and it might be solved already with betas later this year.

Revision history for this message
sathya (bksathyamoorthy) said : 		#8

Sounds good :)
Thanks again for your support.