At 01:44 +0800 04/13/2002, noelle cheng wrote:
>>OK -- that's what's wrong. You're clicking Cast member number 250.
>
>If you say so.
Umm, ... Um. No, not "If I say so"... my impression is that rather
than referencing sprite 250, you're speaking of Cast member number
250, which is not the same thing. Is this in fact what's happening?
If my understanding is not correct, please clarify.
>Now I have another problem. The code is such:
>
>when the screen first appears, some sprites are hidden. On clicking
>on a button, the said related sprite appears. And stays permanently
>on the screen.
>
>If only this was true.
>
>What I see on my screen now:
>
>when I reach this screen, all the sprites are visible.
>
>When I click on a sprite, the related sprite disappears. When I
>click on it again, the related sprite appears.
All right, and what you want to do is start out with given sprites
*not* being visible, correct?
You can add this behavior to those sprites you don't want to be visible:
on beginSprite me
sprite(me.spriteNum).visible = FALSE
END beginSprite
on endSprite me
sprite(me.spriteNum).visible = TRUE
END endSprite
The above should allow any given sprite to not be visible when it
first loads. The other set of scripts should continue working in the
same way (by switching the other sprite's visibility on and off as a
toggle).
--
Warren Ockrassa | http://www.nightwares.com/
Director help | Free files | Sample chapters | Freelance | Consulting
Author | Director 8.5 Shockwave Studio: A Beginner's Guide
Published by Osborne/McGraw-Hill
http://www.osborne.com/indexes/beginners_guides.shtml
[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!]
