In this context it would not matter, but in another context, where you wanted the send command executed after all current scripts terminate, that would be the way to do it. Even if you said, "in 1 second", if the current running script took 3 seconds to terminate, the send command would execute 3 seconds later.
Forgive me if you already knew this. Bob On Feb 1, 2012, at 1:03 PM, Ken Ray wrote: >> on mouseUp >> send "bla" to me in 0 secs >> end mouseUp >> >> and a stack script >> >> on bla >> put the executioncontexts >> end bla >> >> All I get in the message box is one line, referring to the stack. I don't >> think your approach works for Ken Corey. > > Take away the "in 0 secs" and it should work fine (I get two lines, one > referring to the button that issued the 'send' and the other referring to the > stack). I'm guessing the "send in time" aspect messes with the > executionContexts… > > BTW: Why would you send something in 0 secs? Just curious… if you want it to > be processed right away, why not just "send" it? > > Ken Ray > Sons of Thunder Software, Inc. > Email: [email protected] > Web Site: http://www.sonsothunder.com/ > > _______________________________________________ > use-livecode mailing list > [email protected] > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
