I have come across an issue with unlock screen failing to unlock anything. The workaround was to pop a couple of 'wait 0 secs' into my script to allow Rev to catch up.
Shot in the dark but maybe a few 'wait 0 secs' here an there will get your palette to update? Cheers, Steve Scott Rossi wrote: > > Hi List: > > Am I dreaming or did "lock screen" used to affect only the default stack > when implemented? I could have sworn you could lock the screen of one > stack > while doing something in another. > > I have a palette that is supposed to show status of updates occurring in a > topLevel stack while the screen is locked and it seems everything is > locked > because the status is not updating until the end of the handler. > > If lock screen affects everything I guess there's no workaround for > this??? > > Thanks & Regards, > > Scott Rossi > Creative Director > Tactile Media, Multimedia & Design > > > _______________________________________________ > use-revolution mailing list > [email protected] > Please visit this url to subscribe, unsubscribe and manage your > subscription preferences: > http://lists.runrev.com/mailman/listinfo/use-revolution > > -- View this message in context: http://www.nabble.com/Lock-Screen-Changed--tp22798951p22854919.html Sent from the Revolution - User mailing list archive at Nabble.com. _______________________________________________ use-revolution mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
