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 
> <use-livecode@lists.runrev.com> 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 
>> <use-livecode@lists.runrev.com> 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 
>> <use-livecode@lists.runrev.com> 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

Reply via email to