Matt Styles

No, I guess it's not a problem - the requirements are really only there so that elsewhere in the system it's safe to assume an entity has a specific component...

Hm, the resources do pose a problem. I'll give this some further thought (and perhaps ask about a bit). As for entities, assuming the Scene class is loading the file...

RE resources - perhaps it might be possible to have a table which contains resource paths and an ID which marks the path as the kind of resource it is,...

Either way this means the resource management part of xygine needs reworking. For a while now I've also had vague notions of updating the interface to work with resource IDs...

OK, [this is my pass](https://gist.github.com/fallahn/935e0dd7222ead20c367c0c89e30f3dd) at the problem. I figured what really needs to be stored in the editor data is the *source* of resources, ie paths to files on...

Looking good! I've added a few commits just to update the visual studio project and get everything building on Windows. The only query I have is that [here](https://github.com/JonnyPtn/xygine/blob/editor/xyginext/src/core/editor/SpriteEditor.cpp#L405) you appear...

RE: the demo no longer launching on windows - replacing the `renderBuffer` and `textureResource` globals in Editor.cpp with unique_ptrs and creating/destroying then in `Editor::init()` and `Editor::shutdown()` worked around the problem....

Hey, thanks for all your help on this and all your other contributions to xy over the years - it's much appreciated! However, while xy is still a very capable...

use the cmake file with the generator set to MinGW-make, then make as usual https://cmake.org/cmake/help/v3.1/manual/cmake-generators.7.html

Probably related to #59 - the first place to look would probably be how the layer patches are generated for isometric maps. The bounding boxes for these patches are used...