yeah i just noticed that with 1.0.2
I also can't get the Complex exporter to work at all. i just get this error immediately:
TypeError: Error #1034: Type Coercion failed: cannot convert org.flixel::FlxTilemap@54dfeb9 to org.flixel.FlxSprite.
at org.flixel::FlxG$/set state()
Yet i dont see anywhere within addTilemap() that sprite is used at all. ive had this error since i downloaded it and i have absolutely no idea whats going on.
I think I know what might be happening... Are you using the SimpleClaws project as the template? It's probably trying to call onSpriteAddedCallback and pass in the tilemap as a sprite, which would cause the crash. Basically, if you use this in your PlayState it will crash for flixelComplex:
protected function onSpriteAddedCallback(sprite:FlxSprite, group:FlxGroup):void
It should look like this:
protected function onObjectAddedCallback(obj:Object, layer:FlxGroup, level:BaseLevel, properties:Array):void
The SimpleClaws template is meant for use with the flixelSimple exporter and is designed for games where each project contains just the data for one level, the sprites are not rotated or scaled and there is nothing else.
The complexClaws template is the beast! It's meant for use with flixelComplex and will support multiple levels per project, custom properties, rotations, scaling and all of the stuff that's cool but comes with lots more overhead, hence the separation into two different templates.
If you use the PlayState.as file from ComplexClaws that should work...
Let me know how it goes and I'll add a readme to the templates or better yet, add some info to the exporter window itself to make that more clear.
I noticed it doesn't auto associate the project files and you have to manually type .dam when saving.
Is that one bug or two? Ie. are you talking about .dam files not loading when you double click on them as well as the saving bug?
For the saving issue that's an annoying problem with Adobe Air (groan). You can't set a file filter for save dialogs but you can for open dialogs. I don't know why... For now I'll add a fix so that it appends .dam to the filename when the project file save name has no extension.
Let me know about both of those issues and I'll patch up the version with the extra info for the exporting and the saving extension fix. I'll also try and add some better documentation as well.
*EDIT* I just noticed that the flixelComplex exporter doesn't handle scaling (probably because flixel doesn't update scaled collisions automatically). I'm going to remedy that in the next update and try
and handle scaled collisions.