Duplicate simultaneous calls to same handler

[Bob Sneidar]

It would be easy to tell. Start a counter in a local variable before one of the wait with messages statements, increment the counter by one, then after the wait with messages command put the counter into the message box, then subtract one from the counter. If it queues you should see counters going over 1. If not you will only ever see 1. 

Bob S


> On Jan 22, 2015, at 19:26 , J. Landman Gay <jacque at hyperactivesw.com> wrote:
> 
> Suppose I have a long handler that includes a few "wait with messages" so that users can continue interacting with the stack while it runs. The user does something that calls the long handler while it is still running from a previous instance. Assume there is no flag in the script to prevent that.
> 
> Does the engine queue the second call until the long handler finishes, and then send the message from the second call (serial responses)?
> 
> Or does the engine run two instances of the long handler simultaneously? If so, what happens to the values of the variables?
> 
> Or something else?
> 
> I've never allowed this to happen before but I find myself in a position where simultaneous calls would be the best way to handle things.
> 
> -- 
> Jacqueline Landman Gay         |     jacque at hyperactivesw.com
> HyperActive Software           |     http://www.hyperactivesw.com
> 
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode