Accessing Functions in the Script of the Main Stack

Bob Sneidar bobs at twft.com
Wed Aug 24 14:31:10 EDT 2011


I may misunderstand then. I thought that a library stack was enabled with the start using command, and that this is why the scripts run, because the stack script of a stack in use is inserted into the backscript. Am I wrong? If so, then how are the commands and functions in a library stack inserted into the message path?

Bob


On Aug 24, 2011, at 11:04 AM, Ken Ray wrote:

> 
> On Aug 24, 2011, at 12:38 PM, Bob Sneidar wrote:
> 
>> Don't put the functions in the main stack. Put them in another stack called lib_whateveryouwant.livecode. (The name doesn't matter but it's easier to know what you are looking at in the OS that way). Then in your openstack handler start using stack lib_whateveryouwant. This will put the stack script of your library stack in the backscript.
> 
> Actually, I think you meant it will "put the stack script of your library stack *into use*", right? Backscripts are totally different from libraries, as you know...
> 
> Just wanted to clarify for anyone unfamiliar with libraries/backscripts/frontscripts who may be reading this thread,
> 
> Ken Ray
> Sons of Thunder Software, Inc.
> Email: kray at sonsothunder.com
> Web Site: http://www.sonsothunder.com/	
> 
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode





More information about the Use-livecode mailing list