Don’t define onRollOver etc. in MovieClip suclasses

… unless absolutely necessary. Since MC is dynamic, onRollOver, etc. can always be attached at runtime. There is no need to define abstract type of onRollOver whose sole purpose is just to provide an interface for its subclasses to implement. Since once the methods is defined, even without implement, like this:

private function onRollOver(Void):Void{
//to be implemented in subclasses

the class and its subclass instances will automatically become “buttons”. This means if the instances are attached on the stage where they are stacked over other MCs, it will create problems such as flicking when user mouses over the overlapped area.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: