Hey Nate,
As ever, thanks for a real productivity boosting tool, loving it most of the time.
Ok, here's the issue (in laypersons terms). We have created a spine project that is fairly similar to the SpineBoy project using our own ragdoll. Having defined all the slots and attachments, we discovered that some of our images required edits in order for them to sit on the bone as planned. This varied between folder sets of images but once done, the different sized images all sit perfectly on the bones when flipping the images folder. So far so good and exactly as we'd hoped.
However, on exporting the spine json for use in coronasdk, we are finding that the images are not being placed onto the bones (position wise) as they had been inside the GUI editor. We are seeing some torso sections floating into the head section and upper arm sections floating out to the side of the body. Now, I completely understand how this could happen due to the images being different dimensions. However, the fact that they worked inside the GUI, led me to believe that the behaviour would follow when we used the exported json inside corona and changed the images on the slots as required.
Is there some magical property setting that the developer needs to set in order for the images to work in the same way as they do in the GUI?? We don't want to go down the road of mapping different image sizes to the spine json on an adhoc basis, as we literally have 100's of images to work with.
I hope I have explained our predicament clearly and equally hope these is a 'one liner' to solve our woes.
Thanks again for making animation interesting again.
All the best
jim