1) When creating a supertile, right now you cannot place tiles on areas obscured by tiles in the foreground. This makes building/editing large platforms/ramps all but impossible. If you need to say, add an unwalkable tile behind a ramp after you have created a ramp, right now you have to destroy everything and start over, because the tile cannot be placed where foreground objects obscure it.
Suggestion: create a hotkey for toggling 'punch-through' mode. While holding this key - tiles go to the farthest back layer. This would allow you to place tiles on areas obscured by foreground objects.
2) The editor crashes once every 15 minutes or so. This is highly correlated with typing into the search boxes. There is no autosave, so I have lost hours of work.
3) The default of no tiles on the map is wrong. All tiles should default to being walkable. Right now, you must first fill the background layer with walkable tiles (using the flood fill button). Next you place tiles and supertiles on the map. When you remove any of these tiles or supertiles, they leave holes of unwalkable regions. Now, this cannot be fixed with the flood fill, because the whole map will be destroyed.
Suggestion: Either make flood fill smart enough to fill unwalkable/no tile regions OR preferably, when you remove tiles or supertiles replace their footprints with walkable tiles.
4) Supertiles placed on the map cannot be dragged to new locations. Only parts of them move.
5) The testing cycle to see if there are regions where your avatar either goes under objects it should not or on top of objects it should not is extremely long. It requires creating skins, tiles, supertiles, maps, exporting and playing. A nice feature would be to 'test' a map and 'test' a supertile, by placing a stock avatar on every walkable tile, just to be able to see if it looks correct.
6) On exported maps if you used pixel art for a large asset, like a tree, there are many walkable tiles behind the tree that can no longer be clicked. This is because the square bounding box f the pixel art is drawn after those tiles, and is thus in front of them.
Suggestion: Please, please, please, if the area you are clicking is transparent, have the click register on a tile behind that layer. This is probably hard to do, but right now it is impossible to walk through the forest I created because of invisible layers.
7) Navigating the map that you are creating in the editor is hard. If I could use two finger scroll on my mac os x touchpad to scroll both up and down, and sideways, it would be much easier. Right now two finger scroll will not scroll sideways, and is broken on the up and down. It will only scroll down, not up.
When you export a map, there is no feedback. It does not let you know it has succeeded. The button does not disable when you click on it. Also the map will not export until you have saved, closed, and reponed the project at least once.
9) Sometimes, I have a bug with editing skins. At times, although not always, when the horizontal and vertical offsets of skin are modified this change does not propagate through to tiles, and supertiles and maps using this skin. When this happens those tiles and supertiles must be destroyed and recreated.
10) In the example library that we were given, skins that are movie clips are alternating between multiple states, so you can tell that they are movieclips. How did you do that?
11) The editor will not let you set the object id of skins.
Thanks. I would really appreciate if you could fix any/all of these issues. It would make my Openspace editing experience much more enjoyable and productive.
It seems that the stop() action contained on the first frame of those movieclips is ignored when their added on the stage. We hope we will be able to fix this in the future.