Re: Supress Standalone Builder Warnings

Bob: > Thanks for your help and Jacque as well. Very welcome, good topic! But STILL a different/partial implementation – ‘Main stacks’ triggers wrong connotation for you. Not the build stack or the project stack ... but, in your case: > library or behavior stacks Yes, THOSE! Whatever

Re: Supress Standalone Builder Warnings

Hi all, as I already wrote in this thread in the LC forum: -> Maybe the mothership could add another "messageless" application which will create the standalone(s)? See here: > Am 06.05.2024 um 17:39 schrieb Bob Sneidar via use-livecode > :

Re: Supress Standalone Builder Warnings

Hi Curry. Thanks for your help and Jacque as well. I did as you say, in card 1 of the splash stack (which is the stack I build from because I do not have the need to modify it runtime) I have this code in the card script: on closestack --- curryk 2020 no-purge LC build: if the

Re: Supress Standalone Builder Warnings

Bob: > Yes but as I mentioned, that did not work for me. You used something DIFFERENT (a partial implementation) so different results - That’s fine; it’s just not this particular workaround!  I think you misread a code comment, now edited for clarity > I still got the two messages

Re: Supress Standalone Builder Warnings

Yes but as I mentioned, that did not work for me. I still got the two messages after the first build, then messages for ALL my subsequent stack files for build attempts afterwards. I’ll try again tomorrow. Sent from my iPhone > On May 4, 2024, at 02:12, Curry Kenworthy via use-livecode >

Re: Supress Standalone Builder Warnings

Thus, I'm pleased to have created the only (?) complete lower-code workaround for smooth standalone building, without needing to do ‘the dance’ to avoid LC purge dialogs, nor tweak many handlers. ;) So here is the authentic tried-and-true workaround code again, with Comments Edited for

Re: Supress Standalone Builder Warnings

Yeah I do that now. Maybe I’m just majoring in the minors, but it ought to just work out of the box, and it irks me that it doesn’t. The Dev team ought to have one dev dedicated to quashing these niggling bugs. Sent from my iPhone > On May 3, 2024, at 17:15, J. Landman Gay via use-livecode >

Re: Supress Standalone Builder Warnings

I get it now. The way I work around this is to close all stacks and remove from memory (or just relaunch LC,) turn off messages in the toolbar, and open the splash stack. That prevents the other stacks from opening. Build the standalone and you shouldn't have any trouble, except for remembering

Re: Supress Standalone Builder Warnings

I think I have solved (but not resolved) the mystery. My main stack has a lot of behaviors, which of course are enumerated in the stackFiles. When the standalone is created, the builder closes the copy of the main stack but it apparently leaves all the COPIES of the behavior stacks in memory.

Re: Supress Standalone Builder Warnings

Okay I think I traced the issue down to the fact that I “start using” a LOT of stacks, 64 to be exact, and I think that includes all the behaviors as well as the libraries. When I quit (or Livecode deletes) the mainStack, it does NOT delete all the stacksInUse. I think my solution will be to

Re: Supress Standalone Builder Warnings

Jacqueline: > In that case, I'll have to try it next time. Yes, not merely a suggestion; already works with SB here. :) > I get the same results as Curry, > I get two dialogs complaining there are open stacks Not as Curry; that's due to a partial implementation. See follow up. But you are

Re: Supress Standalone Builder Warnings

Well I gave that a try, only using your method in the splash stack. I get the same results as Curry, I get two dialogs complaining there are open stacks on the second platform build, then when I try to open the Main Stack without quitting and relaunching Livecode, I get the dialog for every

Re: Supress Standalone Builder Warnings

In that case, I'll have to try it next time. -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com On May 3, 2024 1:13:03 PM Curry Kenworthy via use-livecode wrote: Code in use 4 years, no issues; restores LC's own original SB technique!

Re: Supress Standalone Builder Warnings

I think the problem is in the splash stack, which is where the blocking handlers should go. When LC builds a standalone, it clones the one in the IDE and creates the standalone from that. Then it reopens the original which now triggers all the handlers in the original. You don't really need to

Re: Supress Standalone Builder Warnings

Bob: > Okay, well this is better. I only get the dialog twice, > whether or not I delete the main stack or no. > Standalone builder is leaving files open from the standalone > that ought not be left open. Yes, that’s what this last part does - Comments edited for clarity! --- and only if

Re: Supress Standalone Builder Warnings

Okay, well this is better. When building for MacOS and Windows simultaneously, I only get the dialog twice, whether or not I delete the main stack or no. But if I leave Livecode running and then try to open the main stack, I get all the dialogs. I think the problem is that the Livecode

Re: Supress Standalone Builder Warnings

Bob: > put this in the closeStack of the splash stack or the main stack? As it says - the 'stack to build' - saving standalone from. > Also, isn’t the problem that when opening a stack Livecode detects > the stack being opened has the same name as one already in memory? As Jacqueline said:

Re: Supress Standalone Builder Warnings

OK so in the process of all this, my original stack Forms Generator 8 has been OVERWRITTEN with the version the Standalone Builder created. So… anybody on this list do NOT follow the instructions in this thread, unless you make backups of all your stacks first, which thankfully I have done.

Re: Supress Standalone Builder Warnings

Also, isn’t the problem that when opening a stack Livecode detects the stack being opened has the same name as one already in memory? Bob S > On May 3, 2024, at 9:39 AM, Bob Sneidar via use-livecode > wrote: > > Hi Curry. > > I use a Splash Stack which then opens what I call the

Re: Supress Standalone Builder Warnings

Hi Curry. I use a Splash Stack which then opens what I call the mainStack. Should I put this in the closeStack of the splash stack or the main stack? Bob S On May 3, 2024, at 8:38 AM, Curry Kenworthy via use-livecode wrote: Simplest way – In card 1 of main stack to build: on closestack

Re: Supress Standalone Builder Warnings

I did the pre’s as well. What about “before”? Bob S > On May 3, 2024, at 9:29 AM, J. Landman Gay via use-livecode > wrote: > > I think the pre* handlers would need it too but try without and see how it > goes. It depends on where they are in the message hierarchy. > > -- > Jacqueline

Re: Supress Standalone Builder Warnings

I think the pre* handlers would need it too but try without and see how it goes. It depends on where they are in the message hierarchy. -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com On May 3, 2024 10:29:13 AM Bob Sneidar via

Re: Supress Standalone Builder Warnings

Unfortunately that is not working. I put the function that checks in the script of the mainStack, and that script gets set as a backScript on preOpenstack so that all the handlers in that stack are available in a Windows standalone (when the Windows builder breaks out all the sub stacks, the

Re: Supress Standalone Builder Warnings

Bob: > I have about had it with the Standalone asking me if I want to > save, purge or cancel for stacks that are already open. Simplest way – In card 1 of main stack to build: on closestack --- curryk 2020 no-purge LC build: if the environment is "development" then lock messages

Re: Supress Standalone Builder Warnings

Hi Marty. I really do want to convert to Levure, but I had a lot of refactoring to do to completely cut over to Andre’s Publish and Subscribe framework before I do that, and I am waiting until that is completed. I am just at the point now, so maybe that will be my next project. Bob S > On

Re: Supress Standalone Builder Warnings

Hi Jacque. I did attempt to deploy this solution a while back, but for whatever reason it failed to work, but I’m sure I missed something. I’m curious, should this also be applied to (pre) openCard / closeCard handlers as well? Thanks this is the simplest explanation I have seen. Bob S >

Re: Supress Standalone Builder Warnings

I build my complex apps using Trevor’s Levure Framework and never have an issue. If you don’t want to go that route, maybe there’s something in the framework you could borrow? --- Marty Knapp > On May 2, 2024, at 5:40 PM, J. Landman Gay via use-livecode > wrote: > > It's this: >

Re: Supress Standalone Builder Warnings

It's this: The engine used to lock messages when building a standalone but that was changed 4 years ago. Personally I think it causes more problems than it solves, but the solution is to add