Charles Hartman wrote:
I seem to remember hitting that cursor bug. The solution had something
to do with resetting the Rev cursors . . . can't remember. Does this
sound familiar to somebody who knows more?
Yes. It happens on Windows machines on various occasions. The command to
use is:
reset cursors
The stack should do this as early as it can when opening, in an "on
startup" handler if possible.
--
Jacqueline Landman Gay | [EMAIL PROTECTED]
HyperActive Software | http://www.hyperactivesw.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
