I was (happily) surprised today when in a handler in a library that was put into use on init of the app
that a handler in lib_initMyApp.livecodescript # now in the msg hierarchy on bakeBread pDaKin put the name of this stack end bakeBread Then in a top level binary stack name… e.g. baking.livecode if we call "bakeBread" we see stack "baking.livecode" in the msg box and not lib_initMyApp.livecodescript ergo "this stack" in a script only text stack in the message path is not seen as "itself" but actually the target script from whence the command was issued. So this means we don't have to parse for "the target" yay! Am I right? Is this dependable moving forward? Any caveats? BR _______________________________________________ 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
