Hi Nate,
to get the project working I had to copy the spine-lua folder under the Spine-Runtimes-master folder into the spine-corona project (Not the folder). Once that was done the application started working. Question, if there are dependencies on these files why was it not include?
As for as the Atlas, can you please provide an example on how to properly use it. I am sure there are a few people like me that is new to this and would like to know the right way of setting it up.
Thank you,
JCP
Because I don't want to include the same files multiple times in the repo. This is true for other runtimes, such as spine-love, spine-unity, spine-2ktd.
I'll look at including an atlas example. The problem is Corona doesn't use name regions, which makes it a huge pain.
Hi Nate,
have you looked at including an atlas example?
Thanks,
JCP
Sorry, I haven't had a chance. Have you tried using the new functions to do it?
Couple of Atlas questions for Corona if I can ask:
a) Does the Corona Runtime support Atlas at this stage?
b) The main usage of Atlas is effectively using sprite sheets instead of individual images correct? If the runtime does support it is there a working Corona project example? (I note in the sample code I'm trying it seem to just work having individual images in a directory)
c) How does the "Bounding Box" functionality mentioned fit into things here & what is it for? I was assuming the Corona Runtime doesn't yet support any automated generation of display objects with physics bodies yet, but is this separate to that?
spine-corona doesn't show how to use atlases, but you can do it as described in the posts I linked above in this thread.
Bounding boxes can be used for anything, but typically they are for hit detection and/or physics.
