Has anyone managed to define a shape as the target with the 128 flag? I've managed to define a shape as the ball okay (admittedly only a smaller circle!), but when I try to define the target as a shape then I can't end the level by hitting the ball against it. If I set up the target in the old way then it all works, but my level would look a lot nicer without a red square in it. I also get the "target" shape rolling around due to gravity, which is not something I'd have expected, and would have thought that it would have been static. My code is this:- <!-- Ball --> <dict> <key>type</key><integer>257</integer> <key>color</key><integer>0xfffffffff</integer> <key>x</key><real>279.0</real> <key>y</key><real>390.0</real> <key>radius</key><real>10.0</real> </dict> <!-- Target --> <dict> <key>type</key><integer>129</integer> <key>color</key><integer>0x000000ff</integer> <key>x</key><real>284.0</real> <key>y</key><real>62.0</real> <key>radius</key><real>10.0</real> </dict>
I tried 131 (poly rather than a circle) but it didn't work either. The shape just seems to float about and doesn't act as the target. What do you mean by "activated"? I have:- <key>targetPositionX</key><real>284.0</real> <key>targetPositionY</key><real>62.0</real> But that just puts the target red square over the top of my supposed poly target, which works but looks nasty. I was hoping to avoid the red square altogether as is hinted at by the level pack guidelines.
Hum, forgot to add another little piece of code, so the target really isn't working... Fixed for 0.8 (to be released soon...)
No probs. I figured that with the huge progress you were making each day with this app then it was possible that some bits had not been fully implemented yet! Keep up the excellent work!