Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Spine-TS] Loading Of "Blank" Spine Project Causes Bug In Other Spine Objects #75

Open
shibekin69 opened this issue Aug 23, 2017 · 1 comment

Comments

@shibekin69
Copy link

shibekin69 commented Aug 23, 2017

Ok, this one took me a little longer to discover. When you have a Spine project that's got no slots/attachments visible in the editor, and you have a bunch of bones with a single slot and multiple attachments that serves as skins, when you add this in your project, this will cause other spine objects on stage to bug out and you won't be able to control them anymore.

In the previous version, this wasn't an issue.

EDIT 1: When I add in a static image attachment on the root, the problem doesn't appear.

@shibekin69
Copy link
Author

shibekin69 commented Aug 23, 2017

Please see sample attachment. This includes the "blank" spine project and the output to be tested. The output is 3.7.01. So in my tests, if there really is no attachment shown in the editor (hidden in the tree), this screws up loaded spine objects' positions and controls (For example: you can't control x and y properties).

If at least 1 attachment show in the editor view, this bug doesn't happen.

hidden-skins-test.zip

EDIT 1: When this happens, apparently, the spine object's root aligns to the top left corner of the screen, but you lose control over it if it were added to a group, or variable, something.

@AleBles AleBles added this to To Do in Implement Spine-TS Aug 24, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

No branches or pull requests

1 participant