Hi Steven,
I don't think there are any fixed rules about something like this.
You may also want to take a look at the lock and unlock message
commands when something is occurring that you don't want happening.
All of this kind of stuff is pretty much trial and error.
Good luck,
Joe
On Mar 15, 2008, at 9:17 PM, Steven Axtell wrote:
Joe,
Thanks for checking back on this. I actually read it as "same" -
didn't really notice the "save".
I haven't worked much with the lock screen command much - I'm
definitely not a veteran with Rev. I'm not exactly sure where I
should insert the lock screen / unlock screen commands. I did try
at least putting it in the substack script. I had put in the
following code:
on preOpenStack
lock screen
pass preOpenStack
end preOpenStack
on OpenStack
unlock screen
pass OpenStack
end OpenStack
I did this hoping to lock the screen before the substack opened up.
The mainstack became inactive when the substack opened. I need to
do some more checking on this.
Steve
Steve, i
In rereading my post I see that my eyes let me down once again.
When I said "save technique", I meant "same technique"; I just
don't want you looking/trying some "save" thingie! You probably
figured that out, but just in case.
Good luck,
Joe Wilkins
_______________________________________________
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
