Thanks for everyone's patience in replyin to my tedious, repeated inquiries on
this subject. I've been days and days fumbling with this. As of yesterday, the
mists cleared and finally things are working… I must be super dense as one
would think this could be easier. Any refinements to this feabl
Script only stacks are designed from the IDE's point of view as not needing
to show a stack window - as what would be the point as any changes to the
visible appearance are discarded. Consequently the IDE loads the stack as
an invisible stack, and will often open the script in the script editor
wit
On 7/24/2016 10:56 PM, Sannyasin Brahmanathaswami wrote:
lf you use just use
someStack.livecode
when you open the "stack" (script only) it actually instantiates a
window in the IDE that you can then do cmd-K and it auto opens the
script.
if you double click on the someStack.livecodescript from
True: you can make the file association on hour mac (document/application
binding) for .livecodescript/Livecode
but LC handles it differently
lf you use just use
someStack.livecode
when you open the "stack" (script only) it actually instantiates a window in
the IDE that you can then do cmd-K
On 7/23/2016 4:04 PM, Sannyasin Brahmanathaswami wrote:
) if the extension of the text only stack is ".livecode" then you can
boot that into the IDE or use GO or "start using"
but if you use ".livecodescript" as the extension. then you can't
actually open it in the IDE by double clicking.
I not
I'm still struggling with the initialization of text only stacks/libs into the
message path
A few questions.
1) if the extension of the text only stack is ".livecode" then you can boot
that into the IDE or use GO or "start using"
but if you use ".livecodescript" as the extension. then you can'
