I guess what I am saying is that since test1 did not *explicitly* return anything, the mouseUp handler should put nothing in the message box. However I am discovering that functions *implicitly* return data that the programmer did not tell them to return.
Some find this ok. I find it disturbing especially if what gets returned if nothing else does is whatever the result resolved to last. That is just crazy talk! Bob S On Nov 14, 2014, at 12:58 , dunb...@aol.com<mailto:dunb...@aol.com> wrote: Bob. This seems right. The return in test2 "returns" to the test1 handler, and the next line in that handler executes, going on to test3. This executes, "returning" to test1 as well, and on up to "mouseUp". In other words, the return in test2 does not know about the fact that the whole thing was started in the mouseUp handler. It would cut off any additional lines of code within itself, but not in test1. Craig _______________________________________________ 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
