localToGlobal not returning correct values when in landscape

Sparrow Forum » Troubleshooting

localToGlobal not returning correct values when in landscape

(3 posts) (2 voices)

Started 3 months ago by paulseawa
Latest reply from paulseawa

Tags:

paulseawa
Member

I've followed tutorials of making my game run in landscape mode by rotating root sprite at the top of my view hierarchy, and setting my statusBarOrientation.

The only problem I seem to have is when receive touch events or when I'm trying to map my coordinates from localToGlobal and vice versa, the cooridnates are not rotated as well. Normally I can work around this problem by transforming my coordinates to my orientation like so:

SPPoint *point = [touch locationInSpace:self.root];

Where root is my root object that has the landscape transformation. This is OK but annoying.

But recently I've been trying to use some other peoples extensions and when they try to translate local to global coordinates it ends up messing things up because they are not accounting for this.

Based on whats happening, does anybody know if I'm doing anything wrong? Should my touch events be coming back like that?

Posted 3 months ago #
synergie7
Member
The method you described works OK. I'm using BEScreen which basically creates a sprite that is rotated and all other sub objects are added to the BEScreen sprite (mScreen)

My usage is probably different to yours, but I've been traversing up the display tree to get the correct object to reference e.g
currentPos = [touch locationInSpace:theTarget.parent.parent];
But now that you mention it, I can see I have some inefficiencies in my code, should go back and work out which object theTarget.parent.parent actually is

I suspect you are going to far up the tree, i.e to the very top, but you need to get the location relative to the rotated sprite
Posted 3 months ago #
paulseawa
Member

I use the root sprite when I'm trying to get global coordinates because I know I can depend on it being at 0,0 in the coordinate space. If I wanted other coordinates in a different space I'd use those. But that's unrelated to my question.

My question is, should I really need to be doing this at all, or am I setting up something wrong in my project? As I mentioned in my post, my suspicions arose when I started using other peoples extensions that didn't work in my landscape project.

Are those extensions just buggy, and not written to handle landscape? Or am I just doing something wrong when setting up my project?

Posted 3 months ago #

RSS feed for this topic

Reply

You must log in to post.