Hi,
>There are usually more invidious ways to get into trouble without
realizing it, though. Generally recursion becomes infinite when
its >terminal condition is unmet, or improperly tested for. For example you
could try this:
> on CursIt
> fSomeNum = 1.0
> repeat while fSomeNum > 0
> fSomeNum = fSomeNum / 2.0
> put fSomeNum
> end repeat
> END CursIt
>Even if you carry out the float precision as far as Director can display,
of course, your test condition will never be met. You'll see nothing >but
zeroes but, technically, your number will never reach zero. The above is an
example of pilot error. ;)
But fSomeNum = 1. And anything greater than 1.0 can be divided by 2.0.
Why do you say that there will be nothing but zeros?
Also logically, I am not able to have anything divisible by zero, right?
But what if Director cannot understand that this is the beginning numeral?
I know that it is written that on page 142 that Director is not able to
handle certain types of math properly so how do I go about this?
>> >it is also possible to issue a command that *should* work safely but
does not (having a movie-in-a-window try to do a 'forget' on itself
is >>>an example of this);
>>>Isn't 'forget' the command to use as I understand it from page 448
> > >' forget pwMy Floater
>>This acts like the destruct call you send to a parent script object,
clearing the window's file, location and so on from memory.'
>>Or have I misunderstood what the author was trying to say?
>That looks like one of my variables. Oh wow, it is.
I hope you don't mind.
> No, you understood correctly -- however note that in that section I
didn't issue the 'forget' call from the MIAW contained in the >pwMyFloater
variable.
What will happen if you did?
> It's the Stage that is issuing that forget call. Having the window
forget itself will lead you into trouble.
Why can't a window forget itself?
>>No, it isn't. And the oddest thing is that the hand cursor appears on
some of the screens only (where it's meant to be the arrow).
And >>on other screens in my movie, the arrow appears. How do I explain this?
>Something someplace is making the hand cursor appear. If there are no
Xtras present, it's got to be some piece of Lingo someplace that's >doing
it. Any chance you have a behavior attached someplace that you didn't
notice -- one which does make the hand cursor appear, but >that
inadvertently got attached to some sprite in the misbehaving parts of the
movie?
>OH -- one more thing. If you set the cursor to a hand with something like
mouseWithin,
>and then exit the frame where that is being done, the hand might not
reset. You'd want to make sure to add this behavior to everything >that
changes the cursor:
on endSprite me
cursor -1
end
This will reset the cursor when the frame is exited permanently.
Is it only on mouseWithin? How about mouseUp. MouseEnter and mouseLeave?
But XML is not the only way to build a quiz. Here's something I'm sure was
not built in XML from the nightwares web site:
http://www.the-indigestible.com/forums/GCN_Feedback_Forum/acid-test.html
It was definitely created in Director, though. I saw the Director
Shockwave logo appear when I launched the page.
Would you like to share? Through the use of parent child scripting?
No, actually; it was pretty simple. I can send it to you (offlist) if you
want. The source is not at all complicated. I didn't want (or need)
variable questions or answers. And you're right there was no XML involved.
Thank you, if it does not inconvenience you too much.
>>Why is it that sometimes when I attach more than one behavior to a
sprite, some behaviors don't work properly?
>Well, if there's no change but Director doesn't complain about bad syntax
either, then something else is going on. Is it possible that
the >"rollover" member is the same as the "normal" member? If they look
alike, you wouldn't see a change, after all.
No, there is a state change.
>>I use the parameters of the rollover from the behavior inspector. The
parameters is the list of cast members. In fact the button appears >>on
every screen of the movie e.g. next, back or exit button. Yet why on
some screens the rollovers do not work? Am I doing >>something wrong or
has Director refused to do it properly for me?
>Well, with something like that you'd have to make sure the parameters
were correctly set wherever you used the behavior. Setting it up >once on
one sprite in one set of frames will affect only that sprite in those
frames. It won't have any effect anywhere else in your program.
Yes, I know that. Rather, page 50 does explain it very clearly.
Here I have another question: Based on what I have read it is not advisable
to use ' copy and paste' behaviors?
Thank you
Noelle
[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!]
