Initializing Libraries

[David Bovill]

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
without showing the stack window. If needed you can use "show" or "set the
visible" - toplevel may work as well. Double clicking on a script-only
stack in the finder never produced reliable results for me - so I do this
from within the IDE.

An aspect of this issue is that xxxx.livecodescript stacks are not
registered with Spotlight on OSX - my guess is that the devs need to
register this extension in the Livecode app bundle or similar as well?

On 25 July 2016 at 19:07, J. Landman Gay <jacque at hyperactivesw.com> wrote:

> 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 the finder,
>> it *does* now appear in the open windows (hence it must be in RAM)
>> but there is no stack window as such in the IDE for a .livecodescript
>> stack…so I'm unable to edit this from inside the IDE.
>>
>
> Try "toplevel <stackname>"
>
> These stacks aren't any different from any other you open without using
> "go" -- they are in RAM but you need to specifically display them to work
> with them.
>
> --
> Jacqueline Landman Gay         |     jacque at hyperactivesw.com
> HyperActive Software           |     http://www.hyperactivesw.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
>