IndieLib is a cross-platform Game Graphics engine. Main focus is OpenGL ES 2.0 for mobile iOS operating system, and OpenGL desktop. **NOT SUPPORTED ANYMORE**
zlib License
61
stars
27
forks
source link
Xml paths in animations are not relative to the file #135
Generally a path in an xml file for an animation is like this:
The 'file' attribute will be parsed, and added to the current working path, instead of relative to the file it's loaded from. This makes whole paths fragile, because if the relative path between executable (generally it's the default system working path when app launches), and the resources change because of any reason, there will be an error.
What user wants to do is specify relative to the actual file where the path is written.
Note to self: there can be 2 types of paths: image and Collision. To fix this, maybe look for inspiration in the Spritermanager class, since the Spriter format uses a similary path setup.
Generally a path in an xml file for an animation is like this:
The 'file' attribute will be parsed, and added to the current working path, instead of relative to the file it's loaded from. This makes whole paths fragile, because if the relative path between executable (generally it's the default system working path when app launches), and the resources change because of any reason, there will be an error.
What user wants to do is specify relative to the actual file where the path is written.