Thanks everyone who responded. A library stack works like a charm. I will now
be a dedicated user of the Start Using command.
Regards,
Gregory
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe,
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
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
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
That is interesting. It means that if you had a handler in both the library and
the stack script named the same thing, the library would run first, then the
stack version if the message were passed.
Of course, I can beat you all to the punch by saying, Well don't do that! :-)
Bob
On Aug 24,
Stacks in use place their stack script into the message hierarchy just before
the Home stack script. (In a standalone, Home is your mainstack.) This
retains compatibility with HyperCard.
I don't think that's correct (unless I'm misunderstanding) - my home stack
regularly calls on handlers
The dictionary says that start using puts the scripts before any objects
in the back scripts.
I'm glad I learned a bit more about inserting scripts of individual objects
though. My current library has about 5000 lines of code in it and
navigating around it in the script editor is a pain. The
The other thing to keep in mind is that you are limited to many fewer
backscripts than you are library stacks. Or at least that's how it used to be.
I seem o remember a limit of 10 back scripts in a standalone vs 50 library
stacksinuse. Perhaps that's all been changed?
Chipp Walters
CEO,
On 8/24/11 4:36 PM, Ken Ray wrote:
Stacks in use place their stack script into the message hierarchy
just before the Home stack script. (In a standalone, Home is your
mainstack.) This retains compatibility with HyperCard.
I don't think that's correct (unless I'm misunderstanding) - my
home
Thank you Chipp, good point and I believe the limits are still as you
mentioned. Seems there are twists at every change of direction! This is
another limit that does not exist in the IDE but is enforced for standalones
so it's good to make sure the information is out there so it doesn't get
10 matches
Mail list logo
