That’s why I love this forum.
You never know what you’ll learn each day … there’s always something new. =)
That’s why I love this forum.
You never know what you’ll learn each day … there’s always something new. =)
All right, I’ll put this in the BOK, after I’ve cleaned the SPAM… :bad:
just thought Id throw another version of the pixel menu out which I made before kax posted (beating me to it ;))
What you can do is just takes kax’s file and throw this code in it (I also stole kax’s array - I just had the mc actions stringed out equaling each other :beam: )
Now this versions shorter but the onEnterFrame events are constant. Kax went to the trouble of deleting them when not needed and I commend that - this is just another take on whats doing the same thing.
inx = 40;
outx = 100;
ease = 3;
clips = [menu1, menu2, menu3, menu4, menu5, menu6];
selected = null;
clicked = function(){
selected.targ = inx;
(selected = this).targ = outx;
}
easeTo = function(){
this._x += (this.targ-this._x)/ease;
}
for (i=0; i< clips.length; i++){
clips[**i].onRelease = clicked;
clips[**i].onEnterFrame = easeTo;
clips[**i].targ = inx;
}
I know I’m not supposed to reply in BOK, but THANKS! Great help, guys. I’ve learned a lot from these forums and I appreciate your enthusiasm and expertise in tackling questions like this.
Cheers,
jcs
:: Copyright KIRUPA 2024 //--