Yes, exactly. I simply took the code out of the function handler and used it in place of the function call in the mousedown handler in the button script, and it worked fine. This happened with two quite different functions that accomplished the same result: both of the approaches worked in the Mac IDE, but in both cases the function calls failed in the Windows standalone but moving the code into the calling handler worked fine. Makes no sense to me. The function handlers were in the stack script, though, not in the button, I didn't think to test that aspect of it. But the functions were clearly in the message path -- it worked fine on my MacBook.
-- Peter Peter M. Brigham pmb...@gmail.com http://home.comcast.net/~pmbrig On Aug 29, 2013, at 12:53 AM, Geoff Canyon wrote: > Do you mean that the code is no longer in a function at all, it's just part > of some "build the menu" routine, and that works, but if it's a function, > even in the same object, it's no good? That is odd. > > gc > > Sent from my iPad > > On Aug 28, 2013, at 11:40 AM, "Peter M. Brigham" <pmb...@gmail.com> wrote: > >> It started working fine in the standalone when I put the identical code into >> the calling handlers. > > _______________________________________________ > 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 _______________________________________________ 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
