[Use-revolution] Re: Dead rev stack
Mark MacKenzie (Shaw)
markmac at shaw.ca
Fri Nov 23 18:53:01 CST 2001
Interesting that you should write about this at this moment.
I have what I think is a similar problem which began last evening. I am
running development on a PC WinME.
I would like to know the answers to your questions my self.
When this kind of thing happens in iShell we can open the .k files in a word
process and hunt down the codes involved and hopefully get a working program
back which can then be built back.
I guess we need a "Road Map" on what to look for when using a text editor to
look at the .rev stacks. Something to help us separate out sub-stacks into
either editable projects for error trapping or in a "limb lopping off"
operation to pare the error causing stacks from the main stack so that we
can begin the recovery process.
Maybe we can use the debug abilities of Rev to run defective stacks in a
command line like atmosphere. This may already exist and I just haven't got
familiar with it.
Regards Mark MacKenzie
----- Original Message -----
From: "John Cuccio" <jcuccio at pacbell.net>
To: <use-revolution at www.runrev.com>
Sent: Friday, November 23, 2001 1:50 PM
Subject: Dead rev stack
> This week has been a rev night mare.
> I have a stack with a substack. When I open the substack I get the unknown
> error messagge.I go to the stack prperties, window open fine. Now press
> script tab, the square window show , that has the acutal error, but then
> goes away so I can not see what the error is. Then a messagge commes up,
> witth the stop hand, An unknown error occured. It is possible that a
> property cannot be set to a value you have enteredl. I press the OK
> Same message again I press OK. Then the Stack Properties window is
> So I go to click the script tab again same thing. It just keep repeating
> I can not get any Thing to open.
> If I do not open the substack every things works fine. The Sub stack is
> doing something, but I can not fix it.
> Is there a way to get the scripts out of that stack so that I can load
> into a new stack. So I can figure out what is going on.
> This stack was writen in rev 1.0 Same problem in rev 1.1 and different Mac
More information about the use-livecode