Watch out for 2.6 then going back to 2.5

2005-06-09 Thread Dennis Brown
I switched to 2.6 for a few hours, and during that time I made some edits and saved a stack I have been working on for some months. I switched back to 2.5.1 due to bugs so I could continue development on my stack. The stack acts goofy now. Here is a snippet of code: repeat with j=1 to 20

Re: Watch out for 2.6 then going back to 2.5

2005-06-09 Thread Dennis Brown
I could use some help. I am not sure how to approach trying to recover my stack. I have lots of backups, but I have to go back many revisions to find a stack the does not produce this error (prior to my brief encounter with 2.6). My stack is just one card, but it has many groups and

RE: Watch out for 2.6 then going back to 2.5

2005-06-09 Thread Lynch, Jonathan
I would say try creating a new stack and copying over all of the objects and scripts. Sometimes stacks become corrupted, and this often works to fix that. Sometimes objects become corrupted, and recreating that object might work in that situation. -Original Message- From: [EMAIL

Re: Watch out for 2.6 then going back to 2.5

2005-06-09 Thread Richard Gaskin
Dennis Brown wrote: I could use some help. I am not sure how to approach trying to recover my stack. I have lots of backups, but I have to go back many revisions to find a stack the does not produce this error (prior to my brief encounter with 2.6). If the Rev IDE is not reporting

Re: Watch out for 2.6 then going back to 2.5

2005-06-09 Thread Sarah Reichelt
repeat with j=1 to 20 put j --mssg box contains 1 get Typ[min(i+1+j,DateLines)] --error on this line executing at 11:59:32 AM TypeFunction: error in source expression Objectcard id 1002 Lineget Typ[min(i+1+j,DateLines)] Hintcard id 1002 The error is

Re: Watch out for 2.6 then going back to 2.5

2005-06-09 Thread Dennis Brown
Richard,Sarah,Mark,Jon I found the problem and my face is a bit red. It was not stack corruption, it was a caused by a typo that caused a missing global declaration. The error just by coincidence happened to occur during the few hours I was trying to run on 2.6. I had so many reverts

Re: Watch out for 2.6 then going back to 2.5

2005-06-09 Thread Richard Gaskin
Dennis Brown wrote: Richard,Sarah,Mark,Jon I found the problem and my face is a bit red. It was not stack corruption, it was a caused by a typo That's good news for everyone. Typos are easy to fix, but corruption isn't. Fortunately, given the way Rev handles its files, corrupted stack