Thanks to all for the pointers and advice. I can get this working now with one of the suggested methods or possibly a combination.
As for the issue of the mainstack not being in the behavior ID, I'm glad it's not there, like Monte and wouldn't like to see the software changed to be in line with what the documentation says. This is a documentation bug (I hope!). Pete Haworth
http://www.mollysrevenge.com http://www.sonicbids.com/MollysRevenge http://www.myspace.com/mollysrevengeband On Feb 13, 2011, at 10:06 PM, Mark Wieder wrote: > Monte- > > Sunday, February 13, 2011, 9:05:23 PM, you wrote: > >> I personally like the idea that the behavior doesn't include the >> mainstack name so I can copy the substacks I store my behaviors on >> out of my object library into the standalone at build time without >> anything breaking ;-) > > ! I never thought of that. OK - I have to agree that it's not a bug > then. But it *is* something that should be documented better. And yes, > it would be nice to have a standardized way of converting among the > various id forms. > > -- > -Mark Wieder > mwie...@ahsoftware.net > > > _______________________________________________ > 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
