Big thanks for adding this, and so quickly! After testing it out, it works like a charm.
The only hitch I hit was that I initially tried to use the file generated by the 'save' button within the Texture Packer Settings window, which currently creates a file with no file extension by default. After adding the '.json' manually, the main load button still can't load it, which makes sense since it only saves the texture packer's settings.
Files created through the main Export dialog's 'save' button' are totally functional, though. The issue that occurs is when the user wants to load only their known good texture packer settings, as the save button within that window implies should be possible. Maybe for simplicity's sake in avoiding two different types of export setting save files, both 'save' buttons could generate the same overall save file, but there could be a 'load' button in the Texture Packer Settings window which only reads the immediately relevant portion of the settings file when loading from it.
If that makes sense, of course!
