ild-games / duckling-legacy Goto Github PK

Stuff that the editor cares about, but not the engine or map files

• Collision Types
• Map metadata (width, height, zoom, grid size)
• Tilesheets

• Map width / height
• Grid size
• Zoom level

It should discuss

1. The purpose of the project.
2. How to get started.

Here's an experimental jsfiddle with some thoughts

https://jsfiddle.net/s2o2kauq/5/

If you have entered invalid data in an attribute, then select another entity, the invalid data persists in the form elements.

Blocked by #85

When we merge actions we diff the previous state with the current state. If the only change is an edit to a primitive field then we merge the actions together. The original goal was to use this behavior to merge edits to the same field. We can fix this merge behavior if we instead compare the previous-previous state to the current state. If the two edits touch the same field it will still be a single edit to a primitive field. If they touch different edits it will be an edit to two complex fields and it won't get merged.

One current example that could really benefit from this is drawables and bounding-box for drawables

Blocked by #80

Blocked by #84

Something like a solution explorer in Visual Studio