Re: running handlers
Hi Jon, Dar already mentioned the executionContexts. Another useful function is the pendingmessages. The pendingmessges contains a list of handlers waiting to execute after the send command was executed. Best, Mark -- Economy-x-Talk Consultancy and Software Engineering http://economy-x-talk.com http://www.salery.biz Get your store on-line within minutes with Salery Web Store software. Download at http://www.salery.biz Op 14-okt-2006, om 3:09 heeft Jon Seymour het volgende geschreven: Is there a way to find out the names of all handlers currently running, that is, those that have started but not yet finished? ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
running handlers
Is there a way to find out the names of all handlers currently running, that is, those that have started but not yet finished? ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
Re: running handlers
On Oct 13, 2006, at 7:09 PM, Jon Seymour wrote: Is there a way to find out the names of all handlers currently running, that is, those that have started but not yet finished? There is only one thread in Revolution so all handlers that are currently running are those on the call stack. The top one is triggered by an event or send (and for send I guess the clock change is an event). The rest are called by that directly or indirectly or triggered by an event or send in 'wait ... with messages'. You can see those with the unsupported property executionContexts. You should be able to figure out how to parse it with a little experimenting. Item -1 is the line number within the handler, -2 is the name of the handler and item 1 to -3 is the long id of the object the handler is in. It does miss some handlers. For example, it misses any handlers executing 'wait ... with messages'. (That might be there to solve some other problem.) In some cases you can find the skipped handler but that might take some work. Dar ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
Re: running handlers
On Oct 13, 2006, at 7:48 PM, Dar Scott wrote: Item -1 is the line number within the handler, -2 is the name of the handler and item 1 to -3 is the long id of the object the handler is in. Whoops. I mean for each line with the first line being the top and the bottom line being the one that accessed the executionContexts property. Dar ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
