Another way to handle it would be to retain the mickey hand during development and then allow the user to specify when building a standalone whether to keep it or not. It would be very simple change; if the hand cursor isn't available, Rev uses the system arrow by default. The only thing you have to do to get a standard cursor in a standalone is leave out the hand.
Like the idea, but don't like that implementation: developers might want to use the hand (for instance, to indicate links) but want the default cursor to be an arrow. If the standalone builder takes out the hand then it's not available for browser-type applications, where it's useful.
Possibly use a white-outlined arrow for the pointer tool? (Although I think Windows uses such a cursor for something else.)
My feeling is that if you have to squint at the cursor to figure out which mode you're in - if you even have to think about it - there's a usability problem.
--
jeanne a. e. devoto ~ [EMAIL PROTECTED]
http://www.jaedworks.com
_______________________________________________
use-revolution mailing list
[EMAIL PROTECTED]
http://lists.runrev.com/mailman/listinfo/use-revolution
