Deferred onSelect

Comments:

Author Thread:

Support

Deferred onSelect
Posted: Friday, October 14, 2005 2:47 PM (EST)

The behavior of the listview's onSelect event handler is intentional. The reason being that the onSelect event handler, by design, waits for idle process for the event handler to fire, which in this instance is after the completion of the button's onClick event handler. This explains why the button's onClick event handler is not on the execution stack when the stack is queried in the listview's onSelect event handler. Not to worry, it is possible to achieve the results you're after. To do this, you will need to induce idle process into APL+WIN, which is possible with executing Œwgive with a right argument of 0. This should be be done immediately after assigning the value property for the listview in the button's onClick event handler.

APL2000 Support

davin.church

Deferred onSelect
Posted: Sunday, October 16, 2005 9:04 PM (EST)

Thanks for tracking this down. I'm amazed at this rather odd behavior, since it seems to be the only thing in APL's GUI system that works like this. If it can't be changed due to some underlying bad behavior by Windows, then I hope we can at least get this exceptional behavior documented.