Creating a Function logic for dynamically created XML buttons

Question

Hi!
It's me...... again! Now I've dynamically created some buttons using XML. They're spread around the stage and I've modified a tooltip script to give each button a tooltip on Mouse_Over. But to se the logic and make it work using AS3 is hard (for me). I want a function that accept to parameters: Tooltip text and  Object to tooltip.
In my code I get this error msg when initiating the function on dynamically created buttons:
1118: Implicit coercion of a value with static type flash.display:Sprite to a possibly unrelated type flash.display:MovieClip.
I beleive there are more than one thing here needing a fix.
Can someone have a look and give me a pointer?
Thanks
function contentTooltip(ttt:String, ttclip:MovieClip):void {
    ttclip.addEventListener(MouseEvent.MOUSE_OVER, mouseOverHandler);
    function mouseOverHandler(e:MouseEvent):void {
        ttip.descr.text=ttt;
        ttip.x=stage.mouseX;
        ttip.y=stage.mouseY-15;
        ttclip.addEventListener(MouseEvent.MOUSE_OUT, mouseOutHandler);
        ttclip.addEventListener(MouseEvent.MOUSE_MOVE, mouseMoveHandler);
        ttip.visible = true;
    function mouseOutHandler(e:MouseEvent):void {
        ttip.visible = false;
        ttclip.removeEventListener(MouseEvent.MOUSE_OUT, mouseOutHandler);
        ttclip.removeEventListener(MouseEvent.MOUSE_MOVE, mouseMoveHandler);
    function mouseMoveHandler(e:MouseEvent):void {
        ttip.x=stage.mouseX;
        ttip.y=stage.mouseY-15;
contentTooltip("Scale button",scale_btn);
contentTooltip("Hide button",hide_btn);

Answer 1

I totally agree with what Ned says and suggests. Nevertheless, I would like to support your thinking process.
From the way you wrote the tooltip functionality it is apparent to me that you conceptualize as a programmer. Again, as Ned said, nested functions are evil. BUT, in a way, what classes accomplish is encapsulation/nesting of properties and functions under the same umbrella. It actually feels that what timeline does in general is nesting named functions within a single function we have no access to.
How you wrote the code is actually a blueprint for a class that could handle the functionality. You, perhaps, are very ready to start coding with classes - not on the timeline.
With that said, for the sake of theory, here is how your functionality can be rewritten on timeline:
scale_btn.toolTip = "Scale button";
test_btn.toolTip = "Test button";
hide_btn.toolTip = "Hide button";
scale_btn.addEventListener(MouseEvent.MOUSE_OVER, mouseOverHandler);
test_btn.addEventListener(MouseEvent.MOUSE_OVER, mouseOverHandler);
hide_btn.addEventListener(MouseEvent.MOUSE_OVER, mouseOverHandler);
var overTarget:MovieClip;
function mouseOverHandler(e:MouseEvent):void {
     overTarget = e.currentTarget;
     ttip.descr.text = overTarget.toolTip;
     ttip.x = stage.mouseX;
     ttip.y = stage.mouseY - 15;
     overTarget.addEventListener(MouseEvent.MOUSE_OUT, mouseOutHandler);
     overTarget.addEventListener(MouseEvent.MOUSE_MOVE, mouseMoveHandler);
     setChildIndex(ttip, numChildren - 1);
     ttip.visible = true;
function mouseOutHandler(e:MouseEvent):void {
     ttip.visible = false;
     overTarget.removeEventListener(MouseEvent.MOUSE_OUT, mouseOutHandler);
     overTarget.removeEventListener(MouseEvent.MOUSE_MOVE, mouseMoveHandler); 
function mouseMoveHandler(e:MouseEvent):void {
     TweenMax.to(ttip, .5, { x:stage.mouseX, ease:Quart.easeOut } );
     TweenMax.to(ttip, .5, { y:stage.mouseY - ttclip.height / 2, ease:Quart.easeOut } );
     //ttip.x=stage.mouseX;
     //ttip.y=stage.mouseY-ttclip.height/2;