You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm feeding the parsed level to a build dependency tool and it would be useful for me to get access to the full file paths for external tile sets so that the built level can depend on those too.
Having looked at the code, and unless I'm mistaken, I don't think that this is accessible already. Would it be ok for me to put together a PR to add this?
Idea would be that when creating a tileset, pass the entire path to the external file instead of just the parent folder, store that and provide an access method to it.
Thanks!
The text was updated successfully, but these errors were encountered:
Definitely open to any PRs if you have something that works for you. I’d have to see the changes and think about it some more.
Normally all Tiled files use relative paths(relative to the map file), and pytiled-parser resolves them to absolute filepaths, but for external tilesets I don’t think we currently hold a reference to the actual filepath, we just load the tileset and store it into the map directly as if it was embedded.
If you have an idea for how to store that somewhere that will be useful for you, feel free to submit a PR
I'm feeding the parsed level to a build dependency tool and it would be useful for me to get access to the full file paths for external tile sets so that the built level can depend on those too.
Having looked at the code, and unless I'm mistaken, I don't think that this is accessible already. Would it be ok for me to put together a PR to add this?
Idea would be that when creating a tileset, pass the entire path to the external file instead of just the parent folder, store that and provide an access method to it.
Thanks!
The text was updated successfully, but these errors were encountered: