Recently, Colin Holgate wrote: >> Or maybe this: > > > Your two approaches are basically the same idea as mine, only in yours there > is still no way for the rest of the script to know that the shift was pressed. > You might also need an idle check, or another send, to then inspect the state > of shiftKeyPressed, and to then do something. My email included all of that > too.
Sorry, I'm not following -- the shift state is constantly polled/stored, so why does the script need to care about the state at all? Maybe your script is the same idea as mine :-) Regards, Scott Rossi Creative Director Tactile Media, UX Design _______________________________________________ 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
