Brad Waite <[EMAIL PROTECTED]>
> Why does my cursor change to type 1 when I swap a bitmap in after a
> qtvr? Even when I try to force sprite(1).cursor = 1, it only works
> after 2nd bitmap is
> swapped in. Grrrrrr.
Hi Brad,
I haven't got a qtvr member to test on, but I think this may be due
to Director setting "the cursor of sprite ..." when a qtvr member
is used, and setting it "the cursor of sprite ..." back to -1 (and not
0, as it ought to do) when the qtvr member is swapped out.
Try watching ...
sprite(<your qtvr spriteNumber>).cursor
... in the Watcher window, while you perform the manipulations you
describe. If this is what is happening, use ...
sprite(<your qtvr spriteNumber>).cursor = 0
... immediately after swapping the bitmap in.
For your information, I encountered the the problem I describe with
editable fields and text members, where the cursor of sprite is set to 1
(I-bar), then back to -1 (arrow).
Cheers,
James
[To remove yourself from this list, or to change to digest mode, go to
http://www.penworks.com/LUJ/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!]