Accessing Functions in the Script of the Main Stack
bobs at twft.com
Wed Aug 24 13:38:22 EDT 2011
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. Anything that calls the functions and commands in the library will have access to them now. The advantage to this is of course, any stack you build in the future can take advantage of the scripts you put here.
If you try to start using the mainstack, I am concerned that any calls to the functions and commands there will get called twice, if called from the mainstack or it's substacks.
For further information, read up on the message path and frontscripts and backscripts.
On Aug 24, 2011, at 10:27 AM, Gregory Lypny wrote:
> Hello everyone,
> I have a main stack with one sub-stack and a number other stacks that are stack files of the main stack. I put a bunch of custom functions in the script of the main stack. They can be accessed from the sub-stack but not the other stack files. What do I need to do to be able to call those functions from the stack files?
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
More information about the Use-livecode