Emergency - (sort of) "a stack name with the same name..."

Bridger Maxwell bridgeyman at gmail.com
Mon Jan 22 22:30:44 EST 2007


Hey,
  I have had a few experiences with an answer box popping up, but then
making itself inaccessible, either by hiding itself or by simply lacking an
"OK" button.  Revolution will not let you do anything until you have
responded, and you are unable to respond.  I have been able to fix this by
opening another stack with networking enabled (I found I am still able to
open stacks, even with Rev stuck) and then remote-administering from a
different computer.  This usually includes:
close stack "Answer dialog"
and:
lock messages; wait 5 seconds with messages
I don't know if you happen to have two computers and a good networking stack
lying around, but it is one possibility.  Sorry if this wasn't much help, I
was just sharing how I usually get myself out of that situation.  Best of
luck!

   TTFN
   Bridger
   Christa McAuliffe Space Education Center

On 1/22/07, David Bovill <david at openpartnership.net> wrote:
>
> I have done this so many times - but wandering if someone can tell me how
> to
> get out of it... Rev is stuck in an infinite loop... it keeps infinitely
> saving two files and has the error dialogue stuck in the back. Command
> period and nothing I can think of exits the loop.
>
> I have almost never got out of this without a force quite - and I have
> just
> finished some complex coding. Is there any way to get out of it??? I am
> sure
> you all know what I mean - it happens pretty well all the time if you
> change
> stacks name and then"Save as..."
>
> I can never quite believe that it will do this so occasionally I try a
> "Save as..." - deadly! I'll go and have a beer and hope some guru has a
> hack
> to get out of this?
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-revolution
>



More information about the use-livecode mailing list