On Mar 7, 2005, at 11:44 AM, Lists wrote:
Unfortunately, at least up to MX 2004 (can't recall if that has changed), itCursors are set at the system level. There are several known problems with VR cursor handling and director including one where the cursor gets set to the I beam when you exit a vr sprite span. It is possible using third party tools to embed custom cursor resources inside the VR itself. I sometimes place an invisible sprite slightly larger than the VR onstage with a mouseleave script that resets the cursor. I think the problem is that QTVR sets the cursor behind directors back and this causes director become confused about what the current cursor setting is. Setting the cursor to a value that director believes is the current setting is ignored.
is not possible to take control over QTVR cursors. They are assigned by the
system. The best thing you can try, in my estimation, is to enableHotSpot to
false for a particular hot spot you want to kill. If you only want to
disable/change the cursor, and not the hot spot, I think you're out of luck.
However, I haven't done any VR in 2004, yet, so maybe someone else will
chime in.
--Rich Shupe
rj
[To remove yourself from this list, or to change to digest mode, go to http://www.penworks.com/lingo-l.cgi To post messages to the list, email [email protected] (Problems, email [EMAIL PROTECTED]). Lingo-L is for learning and helping with programming Lingo. Thanks!]
