hello Charles,
In respect to AS 3, I agree with you: create specialized classes is against
OOP, and the idea of having different movieclips being loaded for each
button is good.
The good thing of the old solution (the same used by gugga ff) is that
having all the animations of a button in a sing
Sounds like you are negating the whole purpose of classes.
How about a little reengineering of the buttons.
Build your single class and have multiple instances of the button on screen.
Part of the class would be to load in the proper animation MC for display.
Thus you have the single class that
hello Janis,
the problem is that I don't want several instances of same symbol in the
stage. Imagine a menu for the sections of a site: you have a button, with
some animations, for each section. So, I cann't use several instances of a
same symbol. What I want, and what it was done with AS 2, was
Create simgle clas definition which holds functionality of your "selection
state" and add several instances of same class to stage
2007/3/11, Andrei Thomaz <[EMAIL PROTECTED]>:
hello list,
With AS2, I could associate the same class with several movieclips. This
was
useful, for example, to crea
hello list,
With AS2, I could associate the same class with several movieclips. This was
useful, for example, to create buttons for a menu, when all the buttons were
associated with the same class (some kind of button, that implemented the
'selected' state, rollout and rollover animations, and so
5 matches
Mail list logo
