Hi, the following is a source of frustration for me: when I open stacks via RevNet or RevOnline (or even from my own drive, I think), I always use Close and Remove from Memory, before opening the next stack. But even this doesn't prevent the following from happening:
Using either the Script button or trying to get the script to show via the Inspector, nothing happens. I then have to close Rev but, although I can select Quit, nothing happens either.
I Force Quit, open the "offending" stack, and can get to the scripts, no trouble. So I'm guessing that 9 times out of 10, it's not the stack at fault but Rev, I guess... (although I've had the occassional stack which has frozen Rev completely).
Is this just the way it is (i.e a bug of sorts); or have I missed something in Rev preferences which would prevent this from happening; or might there be a Rev line to put in the Message Box which would put it back on track again to save me having to restart Rev and then find and load the stack again, does anyone know please?
For info: Rev 2.9; PowerPC iMac G5, 10.4.11; 2gb
Example stacks makes RR unresponsive
Moderators: FourthWorld, heatherlaine, Klaus, kevinmiller, robinmiller