[swfmill] Why does swfmill produce extra unneeded definitions?
mail at danielcassidy.me.uk
Wed Jun 16 15:18:22 PDT 2010
On 16 June 2010 20:56, armencho at gmail.com <armencho at gmail.com> wrote:
> I was trying to locate the source of error where a piece of graphic in an
> asset built by swfmill would not coerce to a Sprite derived class. Finally I
> converted swf to xml and saw that swfmill added a sprite within a sprite,
> even though I was embedding a simple SVG consisting of one polygon. The
> swfmill XML looks like this, where you can see two sprite definitions
> instead of one. Is it weirdness or what? :-)
When swfmill imports an SVG, it generates a sprite for every shape within
the SVG. I’m not sure if that is necessarily a good idea, but it is the way
the import has worked for as long as it’s been useful.
The advantage is that you can address individual components of the SVG image
programmatically from ActionScript. A disadvantage is that I assume it’s
probably slower, and perhaps a bit confusing as you’ve found out :).
Hope this helps,
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the swfmill