Closed astrochili closed 3 months ago
Current workflow is designed to "just" import gui or collection and it should import all relative atlases. Also if atlas is updated the reload of binded file should reload all these images.
I think the open & modify atlas directly will be a good thing only if I will support export of all files. Not sure I'll achieve that soon
Aww, I didn't know that when importing a gui it also imports the linked atlas, that's great!
Won't change a current approach
Will keep it as a auto-export option, when working with gui/collections
Maybe I haven't fully figured it out, but it seemed to me that the concept of "atlas" in Panthera is not at all related to atlases in Defold.
If there is already a Defold atlas, it would be convenient to import it and immediately get a full list of available images.
It would also be good to add new pictures to this atlas directly in Panthera, then save and export it, so that it would be updated in Defold version as well.
Perhaps it makes sense to switch to working with
*.atlas
files directly, without the middle*.json
file.