Movieclips with mouse handlers that make them behave as buttons no longer automatically use the lovable hand cursor. Hence the need for these two properties to be set to true on your DisplayList object!
buttonMode = true;
useHandCursor = true;
Movieclips with mouse handlers that make them behave as buttons no longer automatically use the lovable hand cursor. Hence the need for these two properties to be set to true on your DisplayList object!
buttonMode = true;
useHandCursor = true;
I ran into this problem and couldn’t figure out what was going on because I fail miserably:
The solution:
This expression is useful for deleting things from the bottom of the displayList up.
Flash’s built-in filters (eg. blur/drop shadow) can be applied to display objects and bitmaps, though frankly it feels much more straightforward when you’re applying them to a display object instead of a bitmap. But I haven’t done anything with bitmaps yet … so …
All the filters are part of the flash.filters.* class.
Hah, it’s a pretty specific case … but this checks the last item of the display list and removes it if it partially matches (indexOf) the name on the display list item. This requires that the display list item to be given a name.
Yeah. Heh. So I’m keeping this code around, why? It could be used in the program I’m writing now, but it’s not nearly flexible enough as this, which loops through the display list and removes any child with containing a partially match of “deleteme”. Much more flexible, but also more intensive in a complex movie?