• Editor

  • Save Export and Pack Settings by CLI

    inglês

Hello,
Each file has its own unique export setting and pack setting. At the moment, these settings can only be saved through the UI in the editor. Given that our project contains a significant number of spines, we need a way to save settings in bulk and make adjustments to the original parameters. Manually handling this through the editor would be extremely labor-intensive. Would it be possible to support bulk saving via the command line
Thank you for your help.

Related Discussions
...

I'm not sure I understand. If you need to customize the export settings, you can generate the export settings JSON yourself. Save an export settings JSON file from the editor so you can see the format, then modify that JSON as you need for your various exports.

    Nate Different spines may have different parameters. For instance, the scale parameter of one spine's original export setting might be 1.0, while another spine's is 0.8. I would need to set the first spine to 0.5 and the second one to 0.4, scaling both to 50% of their original sizes.

      Right, that's why you can have multiple export JSON settings files. You can have one for each project if you really needed. You don't need the Spine editor to create those, copy/paste one and change the values with a text editor. If you have a script or build system that can generate or modify export settings JSON as needed.

        Nate However, I don't know the original scale setting in the project's export settings JSON unless I save the export file using the editor and modify it based on the original scale parameter. 😭

          What is an "original scale parameter"? Do you mean the scale that was used to export the last time the project was exported? It's not great to rely on that, as it's easily changed or lost by doing an export with a different scale or other settings.

            Nate Yes, the scale in the export settings reflects the value from the last time the project was exported. I know it's not reliable, but it's the closest method to handle the scale for each spine.

              I see, thanks for the explanation. I finally understand your suggestion: if you could from the CLI save off the export JSON for a project's last export, you would then have explicit export settings for all your projects without needing to save the export JSON manually for each one.

              I think it's a good idea. I've created an issue to track it:
              EsotericSoftware/spine-editor760

              We will need to determine the details of how it works. Where does it create the file? Next to the project file as project.export.json?

                Nate Thank you so much for the response. I believe the CLI could use the output path as a parameter, with project.export.json as the default value.