Re: Supress Standalone Builder Warnings

[Curry Kenworthy via use-livecode]

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 stacks are identified via subsequent dialogs.

> I could enumerate all of those and then just have code that
> statically closes each stack.

Yep, that’s the delete part. Only the ones announced in dialogs. If more 
than a couple, use a repeat to test or try each separately.


(MAIN stacks, not substacks, for safety with LC ‘delete stack’!) 

> The SB ought not to do that!

Very true. Reported (again) to LC yet?

Already resolved for my project though, so I will focus on other LC 
issues here, after a break for more AAC setup!


Best wishes,

Curry Kenworthy

Radically Innovative Christian LiveCode Development
"PASSION for Elegant, Efficient Code!"
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

Re: Supress Standalone Builder Warnings

[Klaus major-k via use-livecode]

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 
> :
> 
> 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 environment is “development" then
>  lock messages
>  --- and only if add'l loaded MAIN stacks with issues:
>  try
> save stack "Forms Generator"
> delete stack "Forms Generator"
> # delete stack "XYZ" --- etc
>  end try
>   end if
> end closestack
> 
> The result is the first time I build everything goes smoothly (as it always 
> has.) The SECOND time I build I get an alert dialog for every stack that is a 
> behavior of something in the Main Stack or that I started using (library I 
> guess). 
> 
> The standalone Builder opens COPIES of these stacks to add to the standalone, 
> then LEAVES THEM OPEN IN MEMORY. THAT is the heart of the matter. The SB 
> ought not to do that! (I’m talking to you LC devs.) 
> 
> I suppose I could enumerate all of those and then just have code that 
> statically closes each stack. That is probably what I will do. 
> Deleting the main stack does not delete the COPIES of those library or 
> behavior stacks. 
> In summary the problem is not what is open when I go to build. The problem is 
> what is open after I build.
> Anyway, my thanks again for everyone who offered a suggestion on how to 
> resolve this. Sometime the brute force workaround is the only workaround. 
> 
> Bob S

Best

Klaus

--
Klaus Major
https://www.major-k.de
https://www.major-k.de/bass
kl...@major-k.de


___
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

Re: Supress Standalone Builder Warnings

[Bob Sneidar via use-livecode]

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 environment is “development" then
  lock messages
  --- and only if add'l loaded MAIN stacks with issues:
  try
 save stack "Forms Generator"
 delete stack "Forms Generator"
 # delete stack "XYZ" --- etc
  end try
   end if
end closestack


The result is the first time I build everything goes smoothly (as it always 
has.) The SECOND time I build I get an alert dialog for every stack that is a 
behavior of something in the Main Stack or that I started using (library I 
guess). 

The standalone Builder opens COPIES of these stacks to add to the standalone, 
then LEAVES THEM OPEN IN MEMORY. THAT is the heart of the matter. The SB ought 
not to do that! (I’m talking to you LC devs.) 

I suppose I could enumerate all of those and then just have code that 
statically closes each stack. That is probably what I will do. 

Deleting the main stack does not delete the COPIES of those library or behavior 
stacks. 

In summary the problem is not what is open when I go to build. The problem is 
what is open after I build.

Anyway, my thanks again for everyone who offered a suggestion on how to resolve 
this. Sometime the brute force workaround is the only workaround. 

Bob S


> On May 6, 2024, at 4:48 AM, Curry Kenworthy via use-livecode 
>  wrote:
> 
> 
> 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 after the first build,
> > then messages for ALL my subsequent stack files
> 
> That’s what the last part does: close (‘delete’) any ADDITIONAL problematic 
> main stacks in memory -
> 
> (NOT the build stack again!) - to avoid subsequent dialogs.
> 
> Then ... smooth building, here, ever since.
> 
> Your auto detection effort would be very useful, but just manually identify 
> the SPECIFIC problem stacks, per the dialogs – and ‘delete’ the MAIN stacks 
> thereof in the code.
> 
> If more than a couple main stacks to delete, I would use repeat with a test 
> or try. Likewise, the isBuildingStandalone() function from Panos could 
> provide a more specific closestack trigger if needed for splash stack, but I 
> haven’t tried it in this workaround.
> 
> Whether behaviors or other issues could ever require an extra step, obviously 
> we CAN enjoy the same build experience as pre-2020 SB, by simply using the 
> same techniques! Just as I have.
> 
> > [Standalone Builder] ought to just work out of the box
> 
> YES! Reported (again) to LC yet?
> 
> It is a bug/defect, but that was denied at the time.
> 
> Best wishes,
> 
> Curry Kenworthy
> 

___
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

Re: Supress Standalone Builder Warnings

[Curry Kenworthy via use-livecode]

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 after the first build,
> then messages for ALL my subsequent stack files

That’s what the last part does: close (‘delete’) any ADDITIONAL 
problematic main stacks in memory -


(NOT the build stack again!) - to avoid subsequent dialogs.

Then ... smooth building, here, ever since.

Your auto detection effort would be very useful, but just manually 
identify the SPECIFIC problem stacks, per the dialogs – and ‘delete’ the 
MAIN stacks thereof in the code.


If more than a couple main stacks to delete, I would use repeat with a 
test or try. Likewise, the isBuildingStandalone() function from Panos 
could provide a more specific closestack trigger if needed for splash 
stack, but I haven’t tried it in this workaround.


Whether behaviors or other issues could ever require an extra step, 
obviously we CAN enjoy the same build experience as pre-2020 SB, by 
simply using the same techniques! Just as I have.


> [Standalone Builder] ought to just work out of the box

YES! Reported (again) to LC yet?

It is a bug/defect, but that was denied at the time.

Best wishes,

Curry Kenworthy

Radically Innovative Christian LiveCode Development
"PASSION for Elegant, Efficient Code!"
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

Re: Supress Standalone Builder Warnings

[Bob Sneidar via use-livecode]

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 
>  wrote:
> 
> 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 stronger clarity versus hasty/casual reading!
> 
> Solved AND resolved, these 4 years –
> 
> But of course, needing ANY workaround for LC standalone building is just 
> plain wrong!
> 
> That is awkward and a little creepy; it should indeed work right out of the 
> box without ‘modifying code just to build’ as someone already said it well. I 
> hope EVERYONE will encourage LC to fix this SB issue.
> 
> Meanwhile... Simplest way – In card 1 of main stack to build from:
> 
> on closestack
>--- curryk 2020 no-purge LC build:
>if the environment is "development" then
>   lock messages
>   --- and only if add'l loaded MAIN stacks with issues:
>   try
>  # delete stack "ABC"
>  # delete stack "XYZ" --- etc
>   end try
>end if
> end closestack
> 
> Of course, for a build workaround (or any LC work!) backup your stacks first, 
> and don't mix/match methods without caution or ignore project setup. Read 
> carefully to understand code and comments, and see ‘delete stack’ in LC 
> reference.
> 
> Best wishes,
> 
> Curry Kenworthy
> 
> Radically Innovative Christian LiveCode Development
> "PASSION for Elegant, Efficient Code!"
> 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

Re: Supress Standalone Builder Warnings

[Curry Kenworthy via use-livecode]

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 stronger clarity versus hasty/casual reading!


Solved AND resolved, these 4 years –

But of course, needing ANY workaround for LC standalone building is just 
plain wrong!


That is awkward and a little creepy; it should indeed work right out of 
the box without ‘modifying code just to build’ as someone already said 
it well. I hope EVERYONE will encourage LC to fix this SB issue.


Meanwhile... Simplest way – In card 1 of main stack to build from:

on closestack
--- curryk 2020 no-purge LC build:
if the environment is "development" then
   lock messages
   --- and only if add'l loaded MAIN stacks with issues:
   try
  # delete stack "ABC"
  # delete stack "XYZ" --- etc
   end try
end if
end closestack

Of course, for a build workaround (or any LC work!) backup your stacks 
first, and don't mix/match methods without caution or ignore project 
setup. Read carefully to understand code and comments, and see ‘delete 
stack’ in LC reference.


Best wishes,

Curry Kenworthy

Radically Innovative Christian LiveCode Development
"PASSION for Elegant, Efficient Code!"
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

Re: Supress Standalone Builder Warnings

[Bob Sneidar via use-livecode]

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 
>  wrote:
> 
> 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 to do 
> the dance
___
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

Re: Supress Standalone Builder Warnings

[J. Landman Gay via use-livecode]

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 
to do the dance.


--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On May 3, 2024 5:14:49 PM Bob Sneidar via use-livecode 
 wrote:


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. When I open the original Mainstack, duplicate stacks are still 
open. There seems to be no way to delete (close) the copies, because there 
is no variable it seems that contains the names of all the behavior stacks 
left in memory by the standalone builder. They do not appear in the 
openStacks or the stacksInUse. They are not the same stacks as the 
stackFiles of the original mainstack.


What really needs to happen, and I have said this before, the standalone 
builder needs to keep track of all the files it puts in memory, and then 
close them each time a bild is made for each platform.


This is a bug and I will report it as such.

Bob S


On May 3, 2024, at 1:58 PM, Bob Sneidar via use-livecode 
 wrote:


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 close all the Stack Files of the main stack 
upon closing the Main Stack.


Bob S


___
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

Re: Supress Standalone Builder Warnings

[Bob Sneidar via use-livecode]

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. When 
I open the original Mainstack, duplicate stacks are still open. There seems to 
be no way to delete (close) the copies, because there is no variable it seems 
that contains the names of all the behavior stacks left in memory by the 
standalone builder. They do not appear in the openStacks or the stacksInUse. 
They are not the same stacks as the stackFiles of the original mainstack. 

What really needs to happen, and I have said this before, the standalone 
builder needs to keep track of all the files it puts in memory, and then close 
them each time a bild is made for each platform. 

This is a bug and I will report it as such. 

Bob S
 

> On May 3, 2024, at 1:58 PM, Bob Sneidar via use-livecode 
>  wrote:
> 
> 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 close all the Stack Files of the main stack 
> upon closing the Main Stack. 
> 
> Bob S

___
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

Re: Supress Standalone Builder Warnings

[Bob Sneidar via use-livecode]

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 close all the Stack Files of the main stack upon 
closing the Main Stack. 

Bob S

___
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

Re: Supress Standalone Builder Warnings

[Curry Kenworthy via use-livecode]

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 working on same thing - Have fun!

Easy code, already solved, done. Just hard to type a long discussion -

Can't wait to get AAC app set up better, and do this more often!

Ultimately, though ...

Richard:

> In MC building a standalone was not a disruptive process.
> It shouldn't be in LC either, and certainly shouldn't
> require modifying code just to build.

Best wishes,

Curry Kenworthy

Radically Innovative Christian LiveCode Development
"PASSION for Elegant, Efficient Code!"
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

Re: Supress Standalone Builder Warnings

[Bob Sneidar via use-livecode]

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 stack that I 
start using in the main stack. 

As I said, I think the trick has to be to find a way to save the state of the 
environment before building for a platform, close all non-native stacks, do the 
build, again close all non-native stacks, then restore the stacks from the 
saved environment. I am working on that now and it should be fairly trivial. 

Bob S


> On May 3, 2024, at 12:03 PM, J. Landman Gay via use-livecode 
>  wrote:
> 
> 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 worry 
> about the other stacks, just the one that triggers the opening of the working 
> stack(s). When the SB finishes, it will reopen the splash and the blocks will 
> prevent any other stacks from loading into memory.  That may mean you need to 
> use the message box to trigger the handler that opens the others right after 
> the SB finishes.
> 
> The problem may be that LC doesn't close its own copy properly before 
> reopening the original. I'd submit a bug report and include your stack(s) so 
> they can take a look. Ideally there would be an option or property that would 
> let us decide whether messages should be locked or not. It would be nice if 
> the engine could store variable values, create the standalone with messages 
> locked, and then restore the values after the build.
> 
> I'm not sure Curry's suggestion will work, since the SB manages lockmessages 
> on its own. I've tried scripting a lock messages and it was ignored.
> --
> Jacqueline Landman Gay | jac...@hyperactivesw.com
> HyperActive Software | http://www.hyperactivesw.com
> On May 3, 2024 11:41:24 AM Bob Sneidar via use-livecode 
>  wrote:
> 
>> 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
>> --- curryk 2020 no-purge LC build:
>> if the environment is "development" then
>>lock messages
>>--- and only if add'l main stack issues:
>>try
>>   # delete stack "XYZ"
>>end try
>> end if
>> end closestack
>> 
>> ___
>> 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

___
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

Re: Supress Standalone Builder Warnings

[J. Landman Gay via use-livecode]

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!





___
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

Re: Supress Standalone Builder Warnings

[J. Landman Gay via use-livecode]

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 worry about the other stacks, just the one that triggers the opening of 
the working stack(s). When the SB finishes, it will reopen the splash and 
the blocks will prevent any other stacks from loading into memory.  That 
may mean you need to use the message box to trigger the handler that opens 
the others right after the SB finishes.


The problem may be that LC doesn't close its own copy properly before 
reopening the original. I'd submit a bug report and include your stack(s) 
so they can take a look. Ideally there would be an option or property that 
would let us decide whether messages should be locked or not. It would be 
nice if the engine could store variable values, create the standalone with 
messages locked, and then restore the values after the build.


I'm not sure Curry's suggestion will work, since the SB manages 
lockmessages on its own. I've tried scripting a lock messages and it was 
ignored.

--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On May 3, 2024 11:41:24 AM Bob Sneidar via use-livecode 
 wrote:



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
 --- curryk 2020 no-purge LC build:
 if the environment is "development" then
lock messages
--- and only if add'l main stack issues:
try
   # delete stack "XYZ"
end try
 end if
end closestack

___
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

Re: Supress Standalone Builder Warnings

[Curry Kenworthy via use-livecode]

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 add'l main stack(s) with issues:
try
 # delete stack "ABC"
 # delete stack "XYZ" --- etc
end try

Best wishes,

Curry Kenworthy

Radically Innovative Christian LiveCode Development
"PASSION for Elegant, Efficient Code!"
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

Re: Supress Standalone Builder Warnings

[Bob Sneidar via use-livecode]

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 Standalone builder is leaving files 
open from the standalone that ought not be left open. The Standalone Builder 
should build a list of all the file paths of all open stacks (that are not 
native to Livecode itself) prior to the build, then close them all, then build 
the standalone, then close. any stacks opened in that process, then restore the 
old environment by re-opening the stacks that were open prior to the build. 

That is the only way I can see to make the process as clean as possible. The 
end goal here has to be to leave the environment in the exact state that it was 
prior to building. I doubt that will ever get implemented, but that has to be 
how it works. 

I think I can develop a workaround myself, and will probably do that and share 
it with everyone. 

Bob S


> On May 3, 2024, at 11:10 AM, Curry Kenworthy via use-livecode 
>  wrote:
> 
> 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:
> 
> > The engine used to lock messages when building a standalone
> > but that was changed 4 years ago.
> 
> Bob:
> 
> > make backups of all your stacks first
> 
> Of course, and don't mix/match methods, or ignore your project setup -
> 
> Code in use 4 years, no issues; restores LC's own original SB technique!
> 
> Best wishes,
> 
> Curry Kenworthy
> 
> Radically Innovative Christian LiveCode Development
> "PASSION for Elegant, Efficient Code!"
> 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

Re: Supress Standalone Builder Warnings

[Curry Kenworthy via use-livecode]

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:

> The engine used to lock messages when building a standalone
> but that was changed 4 years ago.

Bob:

> make backups of all your stacks first

Of course, and don't mix/match methods, or ignore your project setup -

Code in use 4 years, no issues; restores LC's own original SB technique!

Best wishes,

Curry Kenworthy

Radically Innovative Christian LiveCode Development
"PASSION for Elegant, Efficient Code!"
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

Re: Supress Standalone Builder Warnings

[Bob Sneidar via use-livecode]

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. 

Bob S


> On May 3, 2024, at 9:44 AM, Bob Sneidar via use-livecode 
>  wrote:
> 
> 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 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
>> --- curryk 2020 no-purge LC build:
>> if the environment is "development" then
>>lock messages
>>--- and only if add'l main stack issues:
>>try
>>   # delete stack "XYZ"
>>end try
>> end if
>> end closestack
>> 
>> ___
>> 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

___
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

Re: Supress Standalone Builder Warnings

[Bob Sneidar via use-livecode]

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 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
>  --- curryk 2020 no-purge LC build:
>  if the environment is "development" then
> lock messages
> --- and only if add'l main stack issues:
> try
># delete stack "XYZ"
> end try
>  end if
> end closestack
> 
> ___
> 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

Re: Supress Standalone Builder Warnings

[Bob Sneidar via use-livecode]

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
  --- curryk 2020 no-purge LC build:
  if the environment is "development" then
 lock messages
 --- and only if add'l main stack issues:
 try
# delete stack "XYZ"
 end try
  end if
end closestack

___
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

Re: Supress Standalone Builder Warnings

[Bob Sneidar via use-livecode]

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 Landman Gay | jac...@hyperactivesw.com
> HyperActive Software | http://www.hyperactivesw.com
> On May 3, 2024 10:29:13 AM Bob Sneidar via use-livecode 
>  wrote:
> 
>> 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
>> 
>> 
>>> On May 2, 2024, at 5:40 PM, J. Landman Gay via use-livecode 
>>>  wrote:
>>> 
>>> 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 (multiple) handlers to your stack to 
>>> avoid the dialog. Most of my stacks work okay without the additions, but if 
>>> you have certain handlers in the message hierarchy you get the dialog. The 
>>> code you need to add is in the link above.
>>> --
>>> Jacqueline Landman Gay | jac...@hyperactivesw.com
>>> HyperActive Software | http://www.hyperactivesw.com
>>> On May 2, 2024 6:58:45 PM Bob Sneidar via use-livecode 
>>>  wrote:
>>> 
 Hi all.
 
 I have about had it with the Standalone asking me if I want to save, purge 
 or cancel for stacks that are already open. I ONLY ever have one version 
 of any stack that is open, unless the Standalone Builder is leaving stack 
 IN the Standalone in memory, which would be breathtakingly bad 
 programming, and I do not think they are doing that.
 
 What I would like to do is edit the library that is popping up that 
 dialog, and setting it to where it always cancels (doesn’t change 
 anything). I know I will have to update the library each time a new 
 release came out but it’s worth it just to avoid the hassle of quitting 
 and relaunching every time a different standalone need to be built.
 
 I tried editing the script of revSaveAsStandalone.livecode in the MacOS 
 bundle, but the word “purge” does not occur in the library. Any idea what 
 library is actually popping up that dialog?
 
 BTW the standalone building IS much faster with 9.6.12 (rc1)
 
 Bob S
 ___
 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
>> 
>> ___
>> 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

___
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

Re: Supress Standalone Builder Warnings

[J. Landman Gay via use-livecode]

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 use-livecode 
 wrote:



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


On May 2, 2024, at 5:40 PM, J. Landman Gay via use-livecode 
 wrote:


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 (multiple) handlers to your stack to 
avoid the dialog. Most of my stacks work okay without the additions, but if 
you have certain handlers in the message hierarchy you get the dialog. The 
code you need to add is in the link above.

--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On May 2, 2024 6:58:45 PM Bob Sneidar via use-livecode 
 wrote:



Hi all.

I have about had it with the Standalone asking me if I want to save, purge 
or cancel for stacks that are already open. I ONLY ever have one version of 
any stack that is open, unless the Standalone Builder is leaving stack IN 
the Standalone in memory, which would be breathtakingly bad programming, 
and I do not think they are doing that.


What I would like to do is edit the library that is popping up that dialog, 
and setting it to where it always cancels (doesn’t change anything). I know 
I will have to update the library each time a new release came out but it’s 
worth it just to avoid the hassle of quitting and relaunching every time a 
different standalone need to be built.


I tried editing the script of revSaveAsStandalone.livecode in the MacOS 
bundle, but the word “purge” does not occur in the library. Any idea what 
library is actually popping up that dialog?


BTW the standalone building IS much faster with 9.6.12 (rc1)

Bob S
___
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


___
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

Re: Supress Standalone Builder Warnings

[Bob Sneidar via use-livecode]

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 script of the mainStack 
is no longer in the message path). 

I then used the Find function to find all the (pre) openStack / closeStack 
handlers and add the statement at the beginning. 

However when I attempt to build for MacOS and Windows, or if I do a second 
build in the same Livecode session, I get the dreaded dialogs over, and over, 
and over. Again. Like 100 times. 

So my initial question is, what library actually pops up that dialog so I can 
force the cancel option every time, or is that something built into the engine? 

Bob S


> On May 3, 2024, at 8:26 AM, Bob Sneidar  wrote:
> 
> 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
> 
> 
>> On May 2, 2024, at 5:40 PM, J. Landman Gay via use-livecode 
>>  wrote:
>> 
>> 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 (multiple) handlers to your stack to 
>> avoid the dialog. Most of my stacks work okay without the additions, but if 
>> you have certain handlers in the message hierarchy you get the dialog. The 
>> code you need to add is in the link above.
>> --
>> Jacqueline Landman Gay | jac...@hyperactivesw.com
>> HyperActive Software | http://www.hyperactivesw.com
>> On May 2, 2024 6:58:45 PM Bob Sneidar via use-livecode 
>>  wrote:
>> 
>>> Hi all.
>>> 
>>> I have about had it with the Standalone asking me if I want to save, purge 
>>> or cancel for stacks that are already open. I ONLY ever have one version of 
>>> any stack that is open, unless the Standalone Builder is leaving stack IN 
>>> the Standalone in memory, which would be breathtakingly bad programming, 
>>> and I do not think they are doing that.
>>> 
>>> What I would like to do is edit the library that is popping up that dialog, 
>>> and setting it to where it always cancels (doesn’t change anything). I know 
>>> I will have to update the library each time a new release came out but it’s 
>>> worth it just to avoid the hassle of quitting and relaunching every time a 
>>> different standalone need to be built.
>>> 
>>> I tried editing the script of revSaveAsStandalone.livecode in the MacOS 
>>> bundle, but the word “purge” does not occur in the library. Any idea what 
>>> library is actually popping up that dialog?
>>> 
>>> BTW the standalone building IS much faster with 9.6.12 (rc1)
>>> 
>>> Bob S
>>> ___
>>> 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
> 

___
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

Re: Supress Standalone Builder Warnings

[Curry Kenworthy via use-livecode]

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
  --- and only if add'l main stack issues:
  try
 # delete stack "XYZ"
  end try
   end if
end closestack

Jacqueline:

> 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.

Indeed; WAY more.

Richard:

> In MC building a standalone was not a disruptive process.
> It shouldn't be in LC either, and certainly shouldn't
> require modifying code just to build.

Amen! Well said.

Best wishes,

Curry Kenworthy

Radically Innovative Christian LiveCode Development
"PASSION for Elegant, Efficient Code!"
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

Re: Supress Standalone Builder Warnings

[Bob Sneidar via use-livecode]

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 May 2, 2024, at 6:20 PM, Marty Knapp via use-livecode 
>  wrote:
> 
> 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:
>> 
>> 
>> 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 (multiple) handlers to your stack to 
>> avoid the dialog. Most of my stacks work okay without the additions, but if 
>> you have certain handlers in the message hierarchy you get the dialog. The 
>> code you need to add is in the link above.
>> --
>> Jacqueline Landman Gay | jac...@hyperactivesw.com
>> HyperActive Software | http://www.hyperactivesw.com
>> On May 2, 2024 6:58:45 PM Bob Sneidar via use-livecode 
>>  wrote:
>> 
>>> Hi all.
>>> 
>>> I have about had it with the Standalone asking me if I want to save, purge 
>>> or cancel for stacks that are already open. I ONLY ever have one version of 
>>> any stack that is open, unless the Standalone Builder is leaving stack IN 
>>> the Standalone in memory, which would be breathtakingly bad programming, 
>>> and I do not think they are doing that.
>>> 
>>> What I would like to do is edit the library that is popping up that dialog, 
>>> and setting it to where it always cancels (doesn’t change anything). I know 
>>> I will have to update the library each time a new release came out but it’s 
>>> worth it just to avoid the hassle of quitting and relaunching every time a 
>>> different standalone need to be built.
>>> 
>>> I tried editing the script of revSaveAsStandalone.livecode in the MacOS 
>>> bundle, but the word “purge” does not occur in the library. Any idea what 
>>> library is actually popping up that dialog?
>>> 
>>> BTW the standalone building IS much faster with 9.6.12 (rc1)
>>> 
>>> Bob S
> 
> ___
> 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

Re: Supress Standalone Builder Warnings

[Bob Sneidar via use-livecode]

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


> On May 2, 2024, at 5:40 PM, J. Landman Gay via use-livecode 
>  wrote:
> 
> 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 (multiple) handlers to your stack to avoid 
> the dialog. Most of my stacks work okay without the additions, but if you 
> have certain handlers in the message hierarchy you get the dialog. The code 
> you need to add is in the link above.
> --
> Jacqueline Landman Gay | jac...@hyperactivesw.com
> HyperActive Software | http://www.hyperactivesw.com
> On May 2, 2024 6:58:45 PM Bob Sneidar via use-livecode 
>  wrote:
> 
>> Hi all.
>> 
>> I have about had it with the Standalone asking me if I want to save, purge 
>> or cancel for stacks that are already open. I ONLY ever have one version of 
>> any stack that is open, unless the Standalone Builder is leaving stack IN 
>> the Standalone in memory, which would be breathtakingly bad programming, and 
>> I do not think they are doing that.
>> 
>> What I would like to do is edit the library that is popping up that dialog, 
>> and setting it to where it always cancels (doesn’t change anything). I know 
>> I will have to update the library each time a new release came out but it’s 
>> worth it just to avoid the hassle of quitting and relaunching every time a 
>> different standalone need to be built.
>> 
>> I tried editing the script of revSaveAsStandalone.livecode in the MacOS 
>> bundle, but the word “purge” does not occur in the library. Any idea what 
>> library is actually popping up that dialog?
>> 
>> BTW the standalone building IS much faster with 9.6.12 (rc1)
>> 
>> Bob S
>> ___
>> 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

___
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

Re: Supress Standalone Builder Warnings

[Marty Knapp via use-livecode]

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:
> 
> 
> 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 (multiple) handlers to your stack to avoid 
> the dialog. Most of my stacks work okay without the additions, but if you 
> have certain handlers in the message hierarchy you get the dialog. The code 
> you need to add is in the link above.
> --
> Jacqueline Landman Gay | jac...@hyperactivesw.com
> HyperActive Software | http://www.hyperactivesw.com
> On May 2, 2024 6:58:45 PM Bob Sneidar via use-livecode 
>  wrote:
> 
>> Hi all.
>> 
>> I have about had it with the Standalone asking me if I want to save, purge 
>> or cancel for stacks that are already open. I ONLY ever have one version of 
>> any stack that is open, unless the Standalone Builder is leaving stack IN 
>> the Standalone in memory, which would be breathtakingly bad programming, and 
>> I do not think they are doing that.
>> 
>> What I would like to do is edit the library that is popping up that dialog, 
>> and setting it to where it always cancels (doesn’t change anything). I know 
>> I will have to update the library each time a new release came out but it’s 
>> worth it just to avoid the hassle of quitting and relaunching every time a 
>> different standalone need to be built.
>> 
>> I tried editing the script of revSaveAsStandalone.livecode in the MacOS 
>> bundle, but the word “purge” does not occur in the library. Any idea what 
>> library is actually popping up that dialog?
>> 
>> BTW the standalone building IS much faster with 9.6.12 (rc1)
>> 
>> Bob S

___
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

Re: Supress Standalone Builder Warnings

[J. Landman Gay via use-livecode]

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 (multiple) handlers to your stack to 
avoid the dialog. Most of my stacks work okay without the additions, but if 
you have certain handlers in the message hierarchy you get the dialog. The 
code you need to add is in the link above.

--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On May 2, 2024 6:58:45 PM Bob Sneidar via use-livecode 
 wrote:



Hi all.

I have about had it with the Standalone asking me if I want to save, purge 
or cancel for stacks that are already open. I ONLY ever have one version of 
any stack that is open, unless the Standalone Builder is leaving stack IN 
the Standalone in memory, which would be breathtakingly bad programming, 
and I do not think they are doing that.


What I would like to do is edit the library that is popping up that dialog, 
and setting it to where it always cancels (doesn’t change anything). I know 
I will have to update the library each time a new release came out but it’s 
worth it just to avoid the hassle of quitting and relaunching every time a 
different standalone need to be built.


I tried editing the script of revSaveAsStandalone.livecode in the MacOS 
bundle, but the word “purge” does not occur in the library. Any idea what 
library is actually popping up that dialog?


BTW the standalone building IS much faster with 9.6.12 (rc1)

Bob S
___
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