Re: corrupted stack

My guess is that lists.runrev.com is running on the on-rev system, > and inherits all the problems that those servers have. > > > > > > ----- > -- > Mark Wieder > ahsoftw...@gmail.com > -- > View this message in context

Re: corrupted stack

specially after a couple of weeks of not being able to post or receive list emails. My guess is that lists.runrev.com is running on the on-rev system, and inherits all the problems that those servers have. - -- Mark Wieder ahsoftw...@gmail.com -- View this message in context: http:

Re: corrupted stack

t;> > I just ran into this, yesterday. I don't know if it matters that I >> > was using glx2 at the time, or not, but it was my foray into using >> > glx2 in about a year. >> > >> > On Sun, Apr 24, 2016 at 12:03 PM, Mark Wieder wrote: >> >

Re: corrupted stack

ing > > glx2 in about a year. > > > > On Sun, Apr 24, 2016 at 12:03 PM, Mark Wieder wrote: > > > >> On 04/21/2016 08:39 PM, Mark Wieder wrote: > >> > >>> I just got my first corrupted stack possibly ever. > >>> > >> > >> Yow

Re: corrupted stack

, Mark Wieder wrote: >> >>> I just got my first corrupted stack possibly ever. >>> >> >> Yow! It's completely repeatable, so I filed bug 17508. Thanks for filing that report, Mark. Just to clarify: the issue is limited to saving in legacy format 2.7 or ea

Re: corrupted stack

#x27;t produced any corrupted stacks for me. Yet. - -- Mark Wieder ahsoftw...@gmail.com -- View this message in context: http://runtime-revolution.278305.n4.nabble.com/corrupted-stack-tp4703722p4709026.html Sent from the Revolution - User mailing list archiv

Re: corrupted stack

I just ran into this, yesterday. I don't know if it matters that I was using glx2 at the time, or not, but it was my foray into using glx2 in about a year. On Sun, Apr 24, 2016 at 12:03 PM, Mark Wieder wrote: > On 04/21/2016 08:39 PM, Mark Wieder wrote: > >> I just got my firs

reposting for Heather: corrupted stack

Cool. I have another corrupted stack (my second since the 8.x release). I'll send this off to the team, but just wanted to post the fact here. It's a bit of a weird thing: the stack is in 2.4 format, and works fine there. But it segfaults in LC8 on both linux and osx. And I removed t

Re: corrupted stack

On 04/21/2016 08:39 PM, Mark Wieder wrote: I just got my first corrupted stack possibly ever. Yow! It's completely repeatable, so I filed bug 17508. -- Mark Wieder ahsoftw...@gmail.com ___ use-livecode mailing list use-livecode@lists.runre

corrupted stack

I just got my first corrupted stack possibly ever. I'm working on a utility in LC8-rc1 and figured out that it might be useful in earlier versions as well. So I set the stackfileversion to "2.4", saved the stack, and opened it in LC 4.6.4. No problems. I then made a small chan

Re: Restore corrupted stack

, while making backups from the Finder. Not until I quit and reopened it did I find out it was bad. Now you've got me worried. I've been working on a LC 7 stack for days too without closing it. Please send your corrupted stack to the QCC so they can fix it before it happens to me too. --

Re: Restore corrupted stack

I’m aware of the tilde file naming while saving a stack. I didn’t see that. I saw this sort of corruption in the past (LC 5 or 6) where a stack functions correctly as far as I could tell while it is open. When it is closed and reopened the corruption message appears. In my case, I left the LC 7

Re: Restore corrupted stack

This happened to me the first time I opened a stack in version 7. Check to see if there is a stack file with a tilde (~) in the name in the same folder as the original stack. When LC attempts to convert a stack, it saves the old stack using a tilde in the name so you can recover if something has

Re: Restore corrupted stack

On 8/14/2015 11:12 PM, Peter Bogdanoff wrote: Yes, I understand the change in stack format. Unfortunately the stack won’t open in any version of LC 7. I always get the stack corrupted dialog. In that case I think the team would like to see the stack, so it's probably time for a bug report. -

Re: Restore corrupted stack

Yes, I understand the change in stack format. Unfortunately the stack won’t open in any version of LC 7. I always get the stack corrupted dialog. Peter > On Aug 13, 2015, at 8:46 AM, J. Landman Gay wrote: > > On August 13, 2015 4:24:33 AM CDT, Peter Bogdanoff wrote: >> >> I was working in LC

Re: Restore corrupted stack

On August 13, 2015 4:24:33 AM CDT, Peter Bogdanoff wrote: > >I was working in LC 7.1 dp 1 and chose to not save a stack, quit, >reopened and got the message. > >On my Mac the TimeMachine backups from earlier in the evening are also >reporting as corrupted. I had also saved a version from the Finde

Restore corrupted stack

Hi, Is there a way to restore a corrupted stack (that is also encrypted)? I was working in LC 7.1 dp 1 and chose to not save a stack, quit, reopened and got the message. On my Mac the TimeMachine backups from earlier in the evening are also reporting as corrupted. I had also saved a version

Re: corrupted stack message

Zip up your corrupt stack and send it in to qual...@livecode.com along with any support files necessary to run the stack. Bob S On Nov 3, 2014, at 20:08 , la...@significantplanet.org wrote: I keep getting this message: There w

Re: corrupted stack message

What LC version are you using to save, and what version to open it afterwards? This message often pops up when you open a stack saved with a newer stackFileVersion in an older LC version, one that doesn't "know" the new version. So if you save a stack with LC 7, and then try to open it with 6,

corrupted stack message

I keep getting this message: There was a problem opening that stack; stack is corrupted, check for ~ backup file Luckily I did have the stack backed up. I copied my backup to the folder (6.1.1 on Windows XP) and made a few changes. Then I saved the stack. When I went to reopen my new stack I

AW: AW: Corrupted Stack

. August 2013 14:34 > An: How to use LiveCode > Betreff: Re: AW: Corrupted Stack > > Hi Again, > > I'm self taught with LiveCode and not very experienced. I don't understand > the Throw/Catch concept so I've never used it. I also don't know what > unicod

Re: AW: Corrupted Stack

Hi Again, I'm self taught with LiveCode and not very experienced. I don't understand the Throw/Catch concept so I've never used it. I also don't know what unicode is. Thanks for the input Tiemo. I exclusively use Macs. So that was a nice try, but unfortunately not the answer. First some backgr

AW: Corrupted Stack

n: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] Im Auftrag > von J. Landman Gay > Gesendet: Montag, 12. August 2013 22:43 > An: How to use LiveCode > Betreff: Re: Corrupted Stack > > On 8/12/13 1:56 PM, Joe Hamburger wrote: > > > Can you think of anyth

Re: Corrupted Stack

On 8/12/13 1:56 PM, Joe Hamburger wrote: Can you think of anything that would cause a force quit? Does lLiveCode actually quit to the desktop? Or do you mean a hang, where the beachball spins forever and you have to manually force-quit? They're caused by different things. If it's the beachb

Re: Corrupted Stack

Joe- Monday, August 12, 2013, 11:56:14 AM, you wrote: > Can you think of anything that would cause a force quit? I tried > lock messages and that didn't help either. You might possibly try putting the statement that puts (or at least tries to) into the field in a try/catch construct and see if t

Re: Corrupted Stack

Hi Jacqueline, You're probably right in that my stack isn't corrupted. I appreciate the help from Mark, Richard and you. All my stacks are set up for the same version of the software, so that isn't the problem. I really don't know what's causing the program to force quit. I've tried everything

Re: Corrupted Stack

On 8/10/13 3:27 PM, Joe Hamburger wrote: The corrupted stack I'm talking about appears fine. I can open any card in it and do whatever I want within the stack. The problem arises when I use a script in another stack to alter the contents of fields in this stack. I don't know if it&#x

Re: Corrupted Stack

Joe Hamburger wrote: > The corrupted stack I'm talking about appears fine. I can open > any card in it and do whatever I want within the stack. The > problem arises when I use a script in another stack to alter > the contents of fields in this stack. ... > My question is,

Re: Corrupted Stack

Joe- Saturday, August 10, 2013, 1:27:23 PM, you wrote: > I don't know if it's a specific field that's the problem or the > stack itself. I can alter all the fields in the bad stack as long as > I do it with a script in the damaged stack. Any chance there's a mismatch in stack versions? Are you t

Re: Corrupted Stack

Hi Richard, Thanks for trying to help. I'm using LiveCode to operate my business. The stacks I've created are exclusively for my use. As such, I don't have access to anything other than the MacOS. The corrupted stack I'm talking about appears fine. I can open any card in

Re: Corrupted Stack

Joe Hamburger wrote: > This is strange. The stack I'm referring to works fine when > everything I do is within the stack. However, when I try to > alter some field data in this stack from a script in another > stack, LiveCode force quits. I have used several different > ways to change the data bu

Corrupted Stack

Hi Everyone, This is strange. The stack I'm referring to works fine when everything I do is within the stack. However, when I try to alter some field data in this stack from a script in another stack, LiveCode force quits. I have used several different ways to change the data but it quits almos