Thanks... I may end up doing it that way if I run out of time here. The only
problem with using a generic tooltip like that is it will overwrite any
rollOver/rollOut code that is already attached to the movieclips. I suppose
I could still use an enterframe and mousecheck, or not be lazy and just
implement it with the existing mouse behavior (haven't given it too much
thought there yet, lots of buttons with rollover code already existing.)
Again thanks... and I agree I don't need a tooltip for every MC, I was kinda
going to use it more for a 'listener' and do a createTextField when needed,
and remove it as needed.
But I still wonder why I can't access the functions in extending a
MovieClip... tooltip or not, this seems like something I could use in the
future.....
Still weaning myself off lingo.......
Jason
----- Original Message -----
From: "Alan Shaw" <[EMAIL PROTECTED]>
To: "Flashcoders mailing list" <[email protected]>
Sent: Wednesday, October 19, 2005 4:17 PM
Subject: Re: [Flashcoders] calling functions in extended movie clip class
I'm giving a link to my ToolTip class which may be of interest to you:
http://nodename.com/blog/2005/09/12/tooltip/
Not that you have to do it all my way, but it may shed light.
Also note that you almost certainly need only a single tooltip in your
application; you can instantiate it the first time it's needed and
then just hide and display it thereafter. It doesn't need to be tied
to the MC it's appearing on top of; it just has to show up in the
right place. See the part of the code that uses localToGlobal() etc.
-A
_______________________________________________
Flashcoders mailing list
[email protected]
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
_______________________________________________
Flashcoders mailing list
[email protected]
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
