Standalone build workaround

[Brian Milby]

And the engine itself can support multiple stacks open with the same name.
If you do though, you have to use the long name to be sure you access the
correct one and the IDE isn't built to always do that.  (I've created a
demo that validates that the engine can handle this.  The engine does
prevent opening different files with the same stack name though, so I had
to clone and then save the clones with different file names but the same
stack name.)

For what Bob mentions, it sounds like the stand alone builder isn't keeping
track of all the stacks that get opened so that it can set destroyStack to
true and close them.  Possibly could be as easy as getting a list of open
stacks at the end and if the long name of any happens to be in the temp
location, then close them before reopening the stack for use in the IDE
post-build.

Brian

On Thu, Sep 20, 2018 at 9:37 AM Bob Sneidar via use-livecode <
use-livecode at lists.runrev.com> wrote:

> When I build a standalone, I use a splash stack, which when run in a
> standalone opens the mainStack. I do not typically have the mainstack
> already open, because as has been mentioned multiple times, any stacks
> already open after a build, say when building for a separate platform (I
> still cannot build for multiple platforms in one pass like I used to) will
> pop up stack already open dialogs and ask me to ignore or purge (no
> uninitiated user wants to "purge" any of his stacks it's quite unnerving
> the first time you see it).
>
> So I always QUIT LC, and relaunch to avoid any stack already open errors.
> What I think is happening is that the copys of the stacks in the standalone
> are being left open, so subsequent opening of the stacks produces this
> error. Otherwise, subsequent opening of the stacks are opening the
> standalone versions instead of the originals because LC gets confused about
> stack name references.
>
> That's just me blind guessing though.
>
> Bob S
>
>
> > On Sep 20, 2018, at 04:40 , Ali Lloyd via use-livecode <
> use-livecode at lists.runrev.com> wrote:
> >
> > Just out of interest, what sorts of things are causing problems in
> > openStack while building a standalone that do not happen when opening
> > stacks for the first time in the IDE? To put it another way, is it simply
> > the re-running of openStack that is causing problems, or is something
> going
> > wrong? Something like a ‘cascade of errors’ sounds like the latter.
> >
> > On Thu, 20 Sep 2018 at 06:11, Curry Kenworthy via use-livecode <
> > use-livecode at lists.runrev.com> wrote:
> >
> >>
> >> Brian:
> >>
> >>> What about a front script for the build process that would
> >>> intercept and discard these messages?
> >>
> >> There you go! That might be a smooth solution. Or close the stack during
> >> build, and offer a user preference of whether to automatically reopen.
> >>
> >> Usually there are some fairly good solutions possible, better than
> >> doubling-down on a dilemma and the lesser of two evils. This could turn
> >> out rather nicely. :)
> >>
> >> Best wishes,
> >>
> >> Curry Kenworthy
> >>
> >> Custom Software Development
> >> LiveCode Training and Consulting
> >> http://livecodeconsulting.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
> >>
> > _______________________________________________
> > 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
>
> _______________________________________________
> 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