OT: Priorities (was: Re: Stack with the same name loop)

On October 6, 2021 9:26:37 PM "Sean Cole \(Pi\) via use-livecode" wrote: I have this thing. I don't know if it's just part of my BPD/EUD or the 48years I've spent on the wrong side of this planet (the outside), I think it's the BPD, but I had to smile at the side of the planet you live on.

Re: Stack with the same name loop

I do something similar but it's a lot less trouble. Save the stack. Go to Finder /Explorer and duplicate it. Rename the copy. Go back to LC and carry on with the original. You can update the name or any properties there. Occasionally as I work I realize that I've implemented a lot of change

Re: Stack with the same name loop

[Huff] and [sigh]! I don't know. I mean, I just don't get it. I don't get how LiveCode get defended as being people that care when they leave something as *basic as this unrepaired for EIGHTTEENYEARS !?! I have this thing. I don't know if it's just part of my BPD/EUD or the 48years I've sp

Re: Stack with the same name loop

My process has become: Save the file in LiveCode. Close the file from LiveCode, purge from memory. Switch to Finder (Mac) or Windows Explorer, or QUIT LiveCode, Duplicate and rename the file, Open the new file, Return to LiveCode, Rename the file in stack properties, if there isa version number in

Re: Stack with the same name loop

On the bright side, it isn't as confusing as the one that tells you the script has been changed in an external editor, even if it wasn't, and then you don't know whether to keep what you're looking at or take a chance and reload. You can lose work by choosing the wrong button. -- Jacqueline La

Re: Stack with the same name loop

On 10/6/21 1:22 PM, Eraklis Pittas via use-livecode wrote: I just put up with it and kill LC - I don't think we will ever have a definitive answer or fix (prove me wrong please!) . As I say they don't seem to eat their own Dog Food otherwise this would have been sorted years ago. That's what

Re: IAP in App Store

I'm confused about how the purchase flow works so my question is probably incorrect. There is no error when I see the "complete" status, it only shows up in my logging file. After adding additional logging, it looks like "complete" is sent after every transaction. But if something goes wrong, li

Re: Stack with the same name loop

Hi Sean, I just put up with it and kill LC - I don't think we will ever have a definitive answer or fix (prove me wrong please!) . As I say they don't seem to eat their own Dog Food otherwise this would have been sorted years ago. While I'm here Somehow the problem with the drop down menus on a

Re: Stack with the same name loop

hehe 😥 Sean On Wed, 6 Oct 2021 at 18:37, Jim MacConnell via use-livecode < use-livecode@lists.runrev.com> wrote: > +1 > > > On Oct 6, 2021, at 10:24 AM, Tom Glod via use-livecode < > use-livecode@lists.runrev.com> wrote: > > > > LOL. me too whenever I get this, I just unplug my comp from

Re: Stack with the same name loop

That's the question of the century that has puzzled most of us. I always tap Purge and it works. As far as I know: Cancel: don't load the new stack, keep the open one, do nothing else Purge: close the open one and remove from memory, open the new stack Save: It's unclear. Save the new one and

Re: Stack with the same name loop

+1 > On Oct 6, 2021, at 10:24 AM, Tom Glod via use-livecode > wrote: > > LOL. me too whenever I get this, I just unplug my comp from the > wall, leave the room, wait for 5 minutes and only then try again. :D > > On Wed, Oct 6, 2021 at 1:18 PM Peter Bogdanoff via use-livecode < > use-l

Re: Stack with the same name loop

LOL. me too whenever I get this, I just unplug my comp from the wall, leave the room, wait for 5 minutes and only then try again. :D On Wed, Oct 6, 2021 at 1:18 PM Peter Bogdanoff via use-livecode < use-livecode@lists.runrev.com> wrote: > Good question. I have no idea either. > > > On Oc

Re: Stack with the same name loop

Good question. I have no idea either. > On Oct 6, 2021, at 12:56 PM, Sean Cole (Pi) via use-livecode > wrote: > > Hi all, > Can someone give the definitive answer as to what to choose when I save my > stack with a save as to create a new iterative version and it comes up with > the prompt : >

Stack with the same name loop

Hi all, Can someone give the definitive answer as to what to choose when I save my stack with a save as to create a new iterative version and it comes up with the prompt : A stack with the same name as the one you are trying to load is already open. SavePurgeCancel Whatev

Re: IAP in App Store

Hello Jacque, What is the exact error that causes purchaseStateUpdate to be sent with a "complete" status? Google is supposed to show its own notification in most cases, so that's fine, but then the purchaseStateUpdate should be sent with an appropriate status anyway. Kind regards, Panos -- On