On Fri, Aug 29, 2014 at 5:58 AM, Trevor DeVore <li...@mangomultimedia.com> wrote:
> Given how dispatch works, I see 'send is' as being what you use if you want > to execute some code after the current event loop has finished executing. > The downside is that the syntax stinks. But if the syntax were updated so > that it supported the same form as dispatch then I think it would be great. > I imagine the engine could also improve the speed to be on par with > dispatch as the engine would know that "someCommand" wouldn't contain any > variables that had to be processed (e.g. "someCommand param1, param2"). > I like that better than the original suggestion to change the dispatch command. Removes the confusion of checking the it and result variables after a call to dispatch with a time on it. One other question regarding send. You can "dispatch function" - is there a way to send a message to a function and get hold of the result (obviously without a time specified)? Pete lcSQL Software <http://www.lcsql.com> Home of lcStackBrowser <http://www.lcsql.com/lcstackbrowser.html> and SQLiteAdmin <http://www.lcsql.com/sqliteadmin.html> _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode