Re: LibraryStack Message

2016-11-28 Thread Bob Sneidar
No close quote Bob S On Nov 23, 2016, at 17:38 , Richard Gaskin mailto:ambassa...@fourthworld.com>> wrote: > start using stack "HelloWorld.livecodescript # ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subs

Re: LibraryStack Message

2016-11-23 Thread J. Landman Gay
The libraryStack handler should only fire when the stack is first put in use. It's like an openstack handler for libraries. Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com On November 23, 2016 4:33:42 PM Sannyasin

Re: LibraryStack Message

2016-11-23 Thread Richard Gaskin
command, but I don't see it inside of any handler, so I can't imagine how it ever gets triggered. I also don't see anything in your mouseUp handler that includes "start using", so I can't imagine how the mouseUp handler could trigger a libraryStack message, or a

Re: LibraryStack Message

2016-11-23 Thread Sannyasin Brahmanathaswami
I guess I am not being clear (hmm I guess this would be easy enough to test, now that I break it down….) helloWorld.livecodescript # stack # contains handler 1 on libraryStack answer "One World, One God" with "OK!" end libraryStack # contains handler 2 on wonderOfWonders A

Re: LibraryStack Message

2016-11-23 Thread Richard Gaskin
Sannyasin Brahmanathaswami wrote: ... > on libraryStack > # do more initialization stuff here that you > # may prefer to encapsulate inside this script > end libraryStack ... > ? this issue is: we don't want the initialization scripts in the > stack to fire everytime it is called, only on the ver

LibraryStack Message

2016-11-23 Thread Sannyasin Brahmanathaswami
if you have a stack in your repository e.g. lib_colorManipulation.livecode # script only that is in the stack files and your initialization script loops through the stack files and for every "lib_*" file it runs start using stack [lib_colorManipulation.livecode] # and any others… these are al