All,
> >
> >NOTE: I mean "exploring the tooltip behaviors" in the sense
> of using them,
> >I'm not of the impression that the behaviors serve as good
> instructional
> >tools.
>
> So, behaviors are not good instructional tools, we would be
> better off writing our own lingo code?
No, that's not my point at all. Do you want to learn how to make tooltips or do you
just want the functionality? If you just want the functionality then use the
behaviors, they work out great if your needs are met and they can save you a lot time.
If you want to learn how to do a given technique things change, the behaviors often
contain lots of extra code that deals with generic behavior authoring and error
checking that can confuse someone trying to learn Lingo.
Saying that the behaviors aren't the best instructional tools in no way equates to you
being better off writing your own. It all depends upon your final goal. What makes you
"better off" or not will depend upon the goal that you are seeking.
A good example is this: do you think you can easily learn how to switch a sprite's
member when the mouse is over it from the behavior? Look at all the code in there just
to teach you this:
on mouseEnter (me)
sprite(me.spriteNum).member = member("rollover")
end
on mouseLeave (me)
sprite(me.spriteNum).member = member("original")
end
The Rollover Member Change behavior has 50+ lines of code in it. A Lingo newbie might
get quite confused and start wondering "do I *need* an isOkToAttach handler?", "what
about this 'getPropertyDescriptionList' handler, what's that do?", and so on.
Does that make more sense? If not then holler and I'll give it another go! :)
Cheers,
Tom
[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!]
