List Index out of bounds (23)

[cholland]

Girder version 3.0.21

"Only send to fist match" seems to be causing the error. When used in conjution with either "Child name" and/or "Child Class" checked.

If I leave "Child Name" and/or "Child Class" checked and I check the "Only send to first match", then click "find", I get a dialogue box stating "List index out of bounds (23)".

If I do a capture, I get the following

Handle: 394768
Parent: 591102
Window Name: Button
Window Class: Afx:400000:3:10011:0:0
Executable: ATIMMC.exe
Wparam: 1
LParam: 589856
Type: Left Click

I then go to the "Target Selector" Window.
I find 4 different Handles to ATIMMC.exe running. I search one of the Handles and I find the matching "Child" Handle 394768.
I click find and 3 Windows show up.
If I click "Child name" or "Child Class", I see multiple buttons. If I leave these checked, it tends to crash my computer since it clicks every button.

So, I narrow the search to just clicking "Only send to first match".
"Name","Class Name", and "Executable" are left checked. This doesn't seem to work.

If I check "Child Name" and/or "Child Class", with the "Only send to first match" and click "Find", I get a dialogue box stating "List index out of bounds (23)".

I'm not sure why the capture doesn't seem to work. The "Test Event" works, but when I press apply and try to test command, it doesn't seem to work. I am trying to tweak the settings, but having troubles. Also, I notice that the LParam changes each time I restart the program.

Thanks for your help.

[Ron]

I've been able to reproduce the first error you describe. So that will be fixed!

The second is really a limitation of windows, Girder has no way of uniquely identifying on of the buttons. If all 5 of the criteria are the same we are out of luck. You should then try to use the keyboard or mouse routines.

And the reason that the "capture window" test event works and the event it selfs is directly linked to this problem. The Capture windows uses the window handle it found while capturing, BUT the normal event tries to find the window handle via the target selector and thus not coming up with the correct on.

Its also a know problem that some program vary their "lParam" and "wParam" all the time, so thats another place that the command capture is not usefull.

-Ron