Hi,
WAS functional, no longer working - it appears to save, but on opening the file the unsaved version runs !
Can't save stack issue
Moderators: FourthWorld, heatherlaine, Klaus, kevinmiller, robinmiller
Re: Can't save stack issue
CAsba.
I am confused. Are you saying that a stack is having this problem in the IDE? That if you modify that stack and save, the changes are not saved at all? And that the only way to save those changes is to "Save as" to a new stack file?
Here is something. If you "Save as..." you are creating a new stack file. I assume (hope) you are renaming that stack file. But know that the stack itself will have the same name unless you change that as well. Have you been changing both?
Craig
I am confused. Are you saying that a stack is having this problem in the IDE? That if you modify that stack and save, the changes are not saved at all? And that the only way to save those changes is to "Save as" to a new stack file?
Here is something. If you "Save as..." you are creating a new stack file. I assume (hope) you are renaming that stack file. But know that the stack itself will have the same name unless you change that as well. Have you been changing both?
Craig
Re: Can't save stack issue
CAsba.
In other words, there are two separate "things" we must deal with. First is the stack file, which is a file on your computer. The "stack" is the LiveCode object that you actually work on, adding buttons, changing colors and saving now and then.
But if you "Save as..." you are only creating a new stack file with the very same stack as its "child". It will be an exact copy of whatever you had when you did that.
Does this help?
Craig
In other words, there are two separate "things" we must deal with. First is the stack file, which is a file on your computer. The "stack" is the LiveCode object that you actually work on, adding buttons, changing colors and saving now and then.
But if you "Save as..." you are only creating a new stack file with the very same stack as its "child". It will be an exact copy of whatever you had when you did that.
Does this help?
Craig
Re: Can't save stack issue
I just encountered the same issue so thought I'd report my findings here.
I had exactly the same errors and issues saving stacks as reported earlier here - and couldn't even use the trick of saving the stack under a different name/location.
The issue? - my own sloppy coding! I had a rogue handler that was opening but not closing database connections to a sqlite db so the open connections were piling up out of control. So, if you do encounter this issue - check it's not something to do with your code causing LC to effectively run out of resources in some way.
Stan
I had exactly the same errors and issues saving stacks as reported earlier here - and couldn't even use the trick of saving the stack under a different name/location.
The issue? - my own sloppy coding! I had a rogue handler that was opening but not closing database connections to a sqlite db so the open connections were piling up out of control. So, if you do encounter this issue - check it's not something to do with your code causing LC to effectively run out of resources in some way.
Stan
Re: Can't save stack issue
Stan.
Are you saying that operator malfunction was somehow involved here?
Craig
Are you saying that operator malfunction was somehow involved here?
Craig
