• EditorBugs
  • Sequence Attachment trims the SPACE at the end of the name

Hey when I use a png Sequence that has name Layer 1,2,3... to convert into sequence attachment it works fine initially but try to rename and without any change click OK in the opened popup, we see the old missing image warning.

The issue is that the SPACE character gets trimmed at the end

  • Misaki ответили на это сообщение.
    Related Discussions
    ...

    The issue you're encountering with the SPACE character being trimmed at the end of the name when using a PNG sequence for a sequence attachment is likely due to how Spine handles attachment names and paths. Spine uses the attachment name for the image path if the path is not specified. If there are spaces or other special characters in the name, it can cause issues with image lookup.

    To avoid this problem, ensure that your attachment names do not have trailing spaces or special characters. You can rename your attachments to remove any trailing spaces. Here’s a step-by-step approach:

    1. Check Attachment Names: Ensure that your attachment names do not have trailing spaces. You can do this by renaming the attachments in Spine.
    2. Use Consistent Naming: Use a consistent naming convention without spaces or special characters. For example, instead of Layer 1, use Layer_1.
    3. Verify Image Paths: Make sure the image paths match the attachment names exactly, without any trailing spaces.

    If you still encounter issues, you can use the Find and Replace feature in Spine to quickly fix attachment names and paths. Here’s a link to the Find and Replace feature in the Spine User Guide.

    Additionally, you can refer to the following GIF for correctly formatting the name in the path field: Sequence Attachment Use.

    If the problem persists, please provide the full name and a screenshot of how you set it in the Sequence properties for further assistance.

    I did eventually went without spaces, but since it was working initially I thought you should know

    warmanw Thank you for your report! I was able to reproduce the issue on my end, so I have created an issue here to fix it: EsotericSoftware/spine-editor813
    We apologize for the inconvenience, but please wait until we have resolved this issue.