Hi Bob,

Did you take into account the release notes (LiveCode 9.4) about Standalone 
Building?

StandaloneBuilding
The standalone builder has always needed to close the stacks it builds for 
reasons pretty deeplyin
grained in the code. 

However this causes a few problems, for example:
- values in script locals become empty
- behaviors are broken when the parent script is on / in a stack which closes

As an attempt to improve this situation, the code that locks messages when 
closing and openingstacks for standalone builds has been removed. 
This means that where previously mainstacks
would not receive any of the (pre)open* and close* messages (e.g. preOpenStack, 
openStack, openCard, closeStack etc) during standalone build, they now do.

If this causes problems for your stack, you can exit from the handler if 
standalone building is inprogress:

on closeStack    
        if the environment is "development" and \      
        there is a stack "revStandaloneProgress" and \      
        the mode of stack "revStandaloneProgress" > 0 then        
                exit closeStack    
        end if
end closeStack

LiveCode 9.0.4 Release Notes 5/10/192

Maybe this will help.

Kind regards,
Erik



-----Original Message-----
From: use-livecode <use-livecode-boun...@lists.runrev.com> On Behalf Of Bob 
Sneidar via use-livecode
Sent: vrijdag 3 april 2020 00:16
To: How to use LiveCode <use-livecode@lists.runrev.com>
Cc: Bob Sneidar <bobsnei...@iotecdigital.com>
Subject: Re: Answer Dialog in Stack now

Also, the standalone builder altered all the paths to my stackFiles as though 
they were in the same folder as the stack itself. They are not.

I’m just going on record here to say the standalone builder at present is 
completely unusable. I’ll file a support ticket.

Bob S


On Apr 2, 2020, at 3:01 PM, Bob Sneidar via use-livecode 
<use-livecode@lists.runrev.com<mailto:use-livecode@lists.runrev.com>> wrote:

Okay crisis temporarily averted. For whatever reason the Standalone Builder 
copied several Livecode UI stacks as substacks of my Mainstack! THAT’S NOT 
SUPPOSED TO HAPPEN!!!!!

Bob S


On Apr 2, 2020, at 2:54 PM, Bob Sneidar via use-livecode 
<use-livecode@lists.runrev.com<mailto:use-livecode@lists.runrev.com><mailto:use-livecode@lists.runrev.com>>
 wrote:

Hi all.

I just created a standalone for a new project for the first time. Now every 
time I open it, it complains that there is already and answer Dialog stack in 
memory! What’s worse, any time I use the form Answer Password I can see what I 
type!!! Livecode Devs, MAKE IT STOP!!! You cannot POSSIBLY expect new users to 
deal with this.

How do I “purge” my stack of the errant Answer Dialog?

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

Reply via email to