show package contents

Mark Smith Mark_Smith at
Fri Dec 3 23:37:09 EST 2010

Thanks Jacqueline.You are a terrific teacher. It not only worked but I
understand it. It is a very clever technique. I am still using the old 'hard
coded' method (as well) because it has the advantage that while I *use* the
stack, and modify it, the notes get written to a common stack (not a "copy"
of the stack where they might get trashed). I hope that makes sense? But
I've created a distribution "startup" (aka splash) that saves the notepad
stack into the startup bundle (using stack panes) and also calls the stack
by the relative pathname. Whew, that was a lot to learn. Thanks

-- Mark

J. Landman Gay wrote:
> In your script, change the hard-coded path to one that calculates the 
> relative path. This function should work whether your notepad stack is 
> opened from the standalone or in the IDE:
> funtion getStackPath pFileName -- i.e. "notepad4"
>    put the effective filename of this stack into tPath
>    set the itemDelimiter to slash
>    put pFileName into last item of tPath
>    return tPath
> end getStackPath
> While developing, you need to put your notepad4 stack into the same 
> folder as the mainstack that will become the standalone, since the 
> function looks in the same folder for the file. In the IDE, that's the 
> folder containing the mainstack. In an OS X standalone, it's inside the 
> bundle next to the standalone executable. On Windows and Linux, which 
> don't have bundles, it's just like in the IDE, and looks for the 
> notepad4 stack in the same folder with the standalone.
> -- 
> Jacqueline Landman Gay         |     jacque at
> HyperActive Software           |
> _______________________________________________
> use-livecode mailing list
> use-livecode at
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
View this message in context:
Sent from the Revolution - User mailing list archive at

More information about the use-livecode mailing list