[swfmill] Why does swfmill produce extra unneeded definitions?
armencho at gmail.com
armencho at gmail.com
Thu Jun 17 12:49:06 PDT 2010
Thanks Dan. Yes, it appears that it is what is going on. A bit strange
though in my case, because i have a very simple svg that simply draws an
"arrow" as a polygon with three vertices:
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<polygon fill="black" points="-5,-2.5 5,-2.5 0,2.5" />
So, in the case above, there is no distinct sprite child to manipulate.
But swfmill still generates a Sprite that contains a Sprite (with runtime
property referencing it) that contains the actual shape graphics. And since
it generates a property with random name like "id*******" (7 random digits
for asterisks), it is also difficult to write a class definition in say haXe
that will match the graphics.
I am not sure what exactly is going on...
But I can leave it be because I typed my class as "dynamic" meaning that the
extra property is not a problem now and can be added at runtime.
On Thu, Jun 17, 2010 at 00:18, Daniel Cassidy <mail at danielcassidy.me.uk>wrote:
> Hi Armencho,
> 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,
> swfmill mailing list
> swfmill at osflash.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the swfmill