Ralph and Curry: Fortunately, I took a break for a week before trying your solutions. For someone who doesn’t do this every day, it is a confusing mess and I suppose that somewhere there is an explanation in the help files of what to do, but my cursory searches didn’t find anything for such a complicated project I was trying to build. Thank heavens for this list!
I also agree that it would be a really good thing if the IDE, or the mothership provided more help for the ever-changing security requirements for Apple mobile and desktop builds. Best, Bill Prothero > On Apr 7, 2021, at 10:20 AM, Ralph DiMola via use-livecode > <use-livecode@lists.runrev.com> wrote: > > I never built a non-mobile standalone for the first 5 years of using LC. For > a mobile build nothing gets closed and gets built from the stack(s) files on > disk. What a surprise I got when I built my first desktop standalone. I > initially thought that something was very wrong with the IDE and restarted. > After some searches I found that this is the correct behavior??? I guess > there is a reason for closing the stack(s) but I find it very odd indeed. > > Ralph DiMola > IT Director > Evergreen Information Services > rdim...@evergreeninfo.net > > > -----Original Message----- > From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On Behalf > Of Curry Kenworthy via use-livecode > Sent: Wednesday, April 07, 2021 1:03 PM > To: use-livecode@lists.runrev.com > Cc: Curry Kenworthy > Subject: Re: Help! I'm stuck > > > Jacqueline: > >> It's not a bug, it was intentionally introduced to allow a couple > of > features, like retaining script local variables after a build. >> Given the amount of extra scripting to work around it for existing > > stacks, I think it may have introduced more problems than it tried > to > cure. > > Agreed! I was too busy the other day but wanted to chime in: > This was a baffling case of doubling-down on a wonky and toxic "fix." > > The problems introduced were far more numerous than those "fixed." > I pointed this out right away, but it seems that hubris prevailed. > LC Ltd needs a more consistent vision of what LC is and how it works. > > Result: workarounds are often needed for standard builds. > In what RAD paradigm should users have to workaround the IDE? > If that's a question we're even needing to ask, we may be in trouble. > > (My own stack design usually makes this a moot point. I wasn't affected. > But I saw the expense and pain this caused, plus a troubling precedent.) > > So ... isn't it great they teach everyone to double down these days? :) > Turning off messages - good tactic, although it won't work for everyone. > > Back to work, take care all.... > > Best wishes, > > Curry Kenworthy > > Custom Software Development > "Better Methods, Better Results" > LiveCode Training and Consulting > http://livecodeconsulting.com/ > > _______________________________________________ > use-livecode mailing list > use-livecode@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@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode William Prothero waproth...@gmail.com _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
