Yes, the see-through case is one that is hard to implement with the
current APIs (because "yaw"/orientation is even more broken than
roll), and I know the new cupcake APIs are expected to make this
specific case much easier.
JBQ
On Mon, Jan 26, 2009 at 2:35 PM, blindfold wrote:
>
> OK, thank yo
OK, thank you JBQ. I was working on a coordinate conversion as needed
to make the relevant angles more intuitive to users when using my app
in a see-through display orientation (similar to Wikitude), and it is
good to know that things will improve with cupcake.
On Jan 26, 11:12 pm, Jean-Baptiste
The issue is that the implementation of the orientation angles in 1.0
isn't actually pitch and roll, it's pitch around the x axis and pitch
around the y axis.
This was deeply improved for cupcake. Yes, we've maintained
compatibility with the old API too.
JBQ
On Mon, Jan 26, 2009 at 1:10 PM, bli
I'm similarly getting more and more confused with the orientation
sensor readings. With my dev phone 1 running in landscape mode, and
the phone standing on its left side, values[1] = 0 and values[2] =
-90. So far so good. Then when I lift the right side of the phone such
that the screen rotates co
4 matches
Mail list logo