• EditorBugs

  • Problem with the tag [merge]

    inglés

Hello, the new version 4.2.23 has an issue with the Import PSD file. I can't import a file to Spine if it includes folders with [merge] as the name. I mean, if the full name of a folder is [merge].

It's an error in the new version only because a few days ago, it worked well for version 4.2.22, and if I select that version to use my Spine, the problem disappears.

I have this structure:

  • Folder: [name:brazoDe*]
    -- Layer: _l1
    -- Layer: _l2
    -- Folder: [merge]

So my images will be named as:

  • brazoDe_l2
  • brazoDe_l1
  • brazoDe

But now I can't import my file (if I use version 4.2.23) because Spine is sending an error for all my folders named [merge].

Is it an update error? I hope it is because I have many folders named [merge].

Or will I need to update how I name my folders to be able to use the import PSD function from now on?

    Related Discussions
    ...

    GuapoMan I have confirmed that I can reproduce the same situation you describe, but it is a bit difficult to determine whether we should allow a folder (layer group) to have only a [merge] tag, even though the [name:] tag is used in the parent folder.

    In the meantime, to give you a solution based on your example, the following should work:

    • Folder: [name:brazoDe*]
    • -- Layer: _l1
    • -- Layer: _l2
    • -- Folder: [!name][merge]brazoDe

    [!name] is a new tag added in 4.2.23. Adding it to a folder name, the folder is no longer affected by the [name] tag of its parent folder.

    We will discuss within the Spine team whether to allow the folder name to have the [merge] tag alone, but even if we decide to allow it in a future release, the notation in the example above should remain valid, so you might want to modify it in that way.

      GuapoMan We have taken this into consideration and will allow empty layer names in the future. Unfortunately, we cannot tell you when the update will be available, but we will let you know when it is.

        GuapoMan

        Thanks for reporting this.
        In general, a layer with no name is invalid, but if it gets a name after a pattern is applied, the new name should be accepted.
        We've restored the previous behavior, and it will be available in the next release.👍️

          Thank you, guys! I'm pleased to hear that this feature will continue to work in future releases. This will help me maintain my current structure, and in my personal opinion, it reduces redundancy in the folder names.

          Also, thanks for the [!name] tag. I didn't understand it when I read about it inside the change log, but now that you wrote about it, I understand how to use it!

            We're happy to help! Thanks for sharing your feedback!

            Aye, the [!name], [!slot], [!bone], and [!path] tags allow you to apply patterns to everything except for a few, otherwise you wouldn't be able to use patterns in some situations and would have to tag every layer.

            Also [bones] is a new addition that can save needing to tag many things with [bone].

            GuapoMan The empty name issue has been fixed in Spine 4.2.24 and is already released! If you have any concerns in the future, please do not hesitate to let us know 🙂

                Misaki Thanks a lot! I already tested it, and it's working well!

                • A Nate le gusta esto.