Ron
October 13th, 2002, 03:55 PM
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
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