Bug when opening another project
Moderator: Klaus
Bug when opening another project
I am running the latest version of livecode. I was working on my one project and went to open my last project to copy and paste some of it and I got the message something like "what do you want to do with the open project? Purge, cancel, save" I choose "save" and my projects both began what looked like a dance, opening and closing and not letting me do anything. I had to shut down the computer and reopen the program. Previously I think I was able to open another project but not now. Is this a bug?
Re: Bug when opening another project
Pugalug.
I have seen this "dance" before, though not in months. Quit LC, and reopen.
Save early, save often.
Nobody really had any experience with it, and no idea what it could mean. Mine is (was) limited to a single project, a mainstack that also carried a handful of subStacks. The dance was always when one or more subStacks was open along with the mainStack, or, more often, when another version of the mainStack was open at the same time.
I have been dance-free all this year.
Craig
I have seen this "dance" before, though not in months. Quit LC, and reopen.
Save early, save often.
Nobody really had any experience with it, and no idea what it could mean. Mine is (was) limited to a single project, a mainstack that also carried a handful of subStacks. The dance was always when one or more subStacks was open along with the mainStack, or, more often, when another version of the mainStack was open at the same time.
I have been dance-free all this year.
Craig
-
- Livecode Opensource Backer
- Posts: 10080
- Joined: Fri Feb 19, 2010 10:17 am
Re: Bug when opening another project
My experience tells me this only happens when both of the projects have the same name.I was working on my one project and went to open my last project
Re: Bug when opening another project
Richmond.
No, though I bet therein lies a clue.
When I see this sort of thing, there are two MainStacks open, and though they are variations of the same project, each has its own stack name and resides in its own uniquely named stack file:
Stack "xyz33" in stack file "xyz33" open at the same time with "xyz32" in stack file "xyz32"
Craig
No, though I bet therein lies a clue.
When I see this sort of thing, there are two MainStacks open, and though they are variations of the same project, each has its own stack name and resides in its own uniquely named stack file:
Stack "xyz33" in stack file "xyz33" open at the same time with "xyz32" in stack file "xyz32"
Craig
Re: Bug when opening another project
The file name on disk doesn't matter, it happens when opening a stack with the same stack name as an existing one. Stacks have three "names" -- the file name, the stack name, and the title. LC tracks only by stack name, the one that shows in the property inspector.
You can open two same-named stacks if you temporarily change the first one in the inspector before opening the second. When done, close the second one and set first one back to the original name.
Easier, and what I usually do, is just open the duplicate in another version of LC where I can copy code or controls. I generally have several versions of LC in my dock.
You can open two same-named stacks if you temporarily change the first one in the inspector before opening the second. When done, close the second one and set first one back to the original name.
Easier, and what I usually do, is just open the duplicate in another version of LC where I can copy code or controls. I generally have several versions of LC in my dock.
Jacqueline Landman Gay | jacque at hyperactivesw dot com
HyperActive Software | http://www.hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
Re: Bug when opening another project
Thanks for the insight everyone. I will look at the names - this could be it!!
Re: Bug when opening another project
Jacque.
Right, but the issues I have had always involve two stacks with two different names.
Craig
Right, but the issues I have had always involve two stacks with two different names.
Craig
Re: Bug when opening another project
If you can reproduce it, it's a bug. I've never seen it happen except when opening same-named stacks, but it would be good to get it fixed if so.
Jacqueline Landman Gay | jacque at hyperactivesw dot com
HyperActive Software | http://www.hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
Re: Bug when opening another project
Jacque.
Are you saying that you saw, with like-named stacks open at the same time, this frenetic continuous opening, closing and reopening of card windows that we are describing here?
I could write a handler that duplicates this "dance", if I wanted to annoy myself.
For me, again, it occurred only with a single LC "project" where I had two stacks open at the same time. But the two stacks always had different names, as in "LEDWorker659" open at the same time as, say, "LEDWorker654". I could read the two versions, posted on the mainStacks as they appeared and disappeared over and over. The issue simply started happening suddenly, oftentimes after quite a while where I was working happily with both. Only force quitting LC made it stop.
I will try to make a video if it ever, er, pops up again.
Craig
Are you saying that you saw, with like-named stacks open at the same time, this frenetic continuous opening, closing and reopening of card windows that we are describing here?
I could write a handler that duplicates this "dance", if I wanted to annoy myself.
For me, again, it occurred only with a single LC "project" where I had two stacks open at the same time. But the two stacks always had different names, as in "LEDWorker659" open at the same time as, say, "LEDWorker654". I could read the two versions, posted on the mainStacks as they appeared and disappeared over and over. The issue simply started happening suddenly, oftentimes after quite a while where I was working happily with both. Only force quitting LC made it stop.
I will try to make a video if it ever, er, pops up again.
Craig
-
- VIP Livecode Opensource Backer
- Posts: 10043
- Joined: Sat Apr 08, 2006 7:05 am
- Contact:
Re: Bug when opening another project
Renaming every stack in a stack file can be onerous.
The long term solution is to remove the scripted IDE restriction on opening stacks of the same name, which appears to have been added to work around a relatively minor engine bug before the team owned the engine. Now they have the means is addressing this in the engine, it would be far simpler for years to restore the functionality MC always enjoyed in which the engine has no such restriction. And given the layers of complexity apparent in the scripted workaround, fixing this one engine detail may ultimately be less expensive for the dev team over over the long haul as well.
https://quality.livecode.com/show_bug.cgi?id=1061
https://quality.livecode.com/show_bug.cgi?id=18793
In the short term, the easiest solution is to keep at least two copies of LC installed (most do anyway, for testing versions), and just opening the second copy of a stack file in a separate LC instance. One can robustly copy even objects between LC instances, so working wl between them is almost as fluid as working within a single instance.
The long term solution is to remove the scripted IDE restriction on opening stacks of the same name, which appears to have been added to work around a relatively minor engine bug before the team owned the engine. Now they have the means is addressing this in the engine, it would be far simpler for years to restore the functionality MC always enjoyed in which the engine has no such restriction. And given the layers of complexity apparent in the scripted workaround, fixing this one engine detail may ultimately be less expensive for the dev team over over the long haul as well.
https://quality.livecode.com/show_bug.cgi?id=1061
https://quality.livecode.com/show_bug.cgi?id=18793
In the short term, the easiest solution is to keep at least two copies of LC installed (most do anyway, for testing versions), and just opening the second copy of a stack file in a separate LC instance. One can robustly copy even objects between LC instances, so working wl between them is almost as fluid as working within a single instance.
Richard Gaskin
LiveCode development, training, and consulting services: Fourth World Systems
LiveCode Group on Facebook
LiveCode Group on LinkedIn
LiveCode development, training, and consulting services: Fourth World Systems
LiveCode Group on Facebook
LiveCode Group on LinkedIn
Re: Bug when opening another project
@Craig: I haven't seen the problem for ages, partly because I have all stacks set to delete from memory on close. It's a setting in preferences so I don't have to think about it. Substacks are never deleted, only mainstacks, so it's the first line of defense but not the only one.
When I do get the warning I usually choose Cancel (don't open) or sometimes Purge (remove the first one) depending on what I need to do. Choosing Save causes the dance. For me, the dialog is a warning. If I need both in the same LC instance I then rename the first one temporarily but that's rare. I'm so used to the conflict now that I just open the second stack in a different copy of LC.
The dialog will tell you which stack is conflicting. It may be a substack, or one you think is closed but is still in memory. If you do see it again I'd be interested in seeing which stack the dialog thinks is the problem.
When I do get the warning I usually choose Cancel (don't open) or sometimes Purge (remove the first one) depending on what I need to do. Choosing Save causes the dance. For me, the dialog is a warning. If I need both in the same LC instance I then rename the first one temporarily but that's rare. I'm so used to the conflict now that I just open the second stack in a different copy of LC.
The dialog will tell you which stack is conflicting. It may be a substack, or one you think is closed but is still in memory. If you do see it again I'd be interested in seeing which stack the dialog thinks is the problem.
Jacqueline Landman Gay | jacque at hyperactivesw dot com
HyperActive Software | http://www.hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
Re: Bug when opening another project
Jacque.
You bring up a point I never considered. Each of the seven subStacks of each uniquely named mainStack are themselves identically named. I have never thought that mattered, since the mainStack is the one that is updated and is the stack that the splash stack navigates to. But it is never one of these subStacks that does the dance, only the mainStack.
That fact may not be pertinent since the problem may only appear to be mainStacks that are causing the dance, because they are the dancers, whereas it is a pair of subStacks that are behind it all.
Hmmm
I do not know what subStack I may be working on that causes this to happen. I will watch more carefully.
Craig
You bring up a point I never considered. Each of the seven subStacks of each uniquely named mainStack are themselves identically named. I have never thought that mattered, since the mainStack is the one that is updated and is the stack that the splash stack navigates to. But it is never one of these subStacks that does the dance, only the mainStack.
That fact may not be pertinent since the problem may only appear to be mainStacks that are causing the dance, because they are the dancers, whereas it is a pair of subStacks that are behind it all.
Hmmm
I do not know what subStack I may be working on that causes this to happen. I will watch more carefully.
Craig