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
The serialization of maps doesn't work properly anymore. Prior to the switch to URLs, it was possible to just save a map XML to a folder (e.g. utiLITI export) and save the external tileset next to it to have a functional map that is compatible with the Tiled editor.
Since we switched to URLs, we're not compatible to the default .tmx format anymore. And the external tilesets can't even be properly exported anymore.
It looks like the tileset is saved under a different partition than the map. Were you trying to export it to a different partition than the original tileset?
Yes, I did. I was exporting it to the Desktop (C:\\...) and my repsitories are on the E:\\ partition as you can see from the example.
I'm not sure if the source property should even contain the absolute path. The original contains a relative path to the tileset (same directory as the map). After the import, the local paths of my machine are backed into the map which basically makes this information useless on any (other) machine with different paths.
I'm truly sorry it took me this long to return to this, but my commitment is a fickle thing.
While I should be responsible for this bug, I don't think I can fix this myself. I'm not familiar enough with UtiLITI. I think this could use a modification to the URLAdapter to handle resources in bundles.
The serialization of maps doesn't work properly anymore. Prior to the switch to URLs, it was possible to just save a map XML to a folder (e.g. utiLITI export) and save the external tileset next to it to have a functional map that is compatible with the Tiled editor.
Since we switched to URLs, we're not compatible to the default .tmx format anymore. And the external tilesets can't even be properly exported anymore.
Original:
After import/export:
Right now, the engine will still find the tileset by name (alias) in these cases but the map is not usable after the export anymore.
We shouldn't introduce anything that makes our .tmx handling different from the default format. I don't see any benefit in this.
We can use URLs internally but we also need to make sure that we stay compatible to the default .tmx format.
This is somewhat related to #273
The text was updated successfully, but these errors were encountered: