Many.

https://projects.maemo.org/bugzilla/show_bug.cgi?id=243822
However no qt feature request filed, for the idea was discussed A LOT 
but not accepted by qt mob sensors / systemInfo folks.

"Default orientation" of the device is the orientation in the boot phase, 
logos and other welcome text must be compliant with this orientation. 
Returned system screen width and height are given fixed in the default 
orientation. 
The default orientation is static and does not change along with the UI 
orientation.
Sensors are fixed to the default orientation.

When UI is in the different orientation than the default orientation,
sensor data must be rotated accordingly. However we do not have any 
programmatic 
means to know when this is to happen, at least I am not aware of.

Admittedly, sticking to ALWAYS-PORTRAIT default orientation kind-of solves the 
problem too. 
Taking into account the wide variety of devices that has been developed in the 
past 
and hopefully will be developed in the future, sticking to any pre-decided 
orientation cannot IMO be done.
(And we already now conflict with the principle: Dali and Lankku, portrait, 
N900 landscape)

- Pia

-----Original Message-----
From: [email protected] [mailto:[email protected]] On 
Behalf Of ext Attila Csipa
Sent: 08 June, 2011 14:23
To: [email protected]
Subject: [MeeGo-dev] Reference UX independent axis orientation

Hi,

How does MeeGo feel about axis orientation in various UX-es ?  There is a a 
reference at http://doc.qt.nokia.com/qt-mobility-
snapshot/qaccelerometerreading.html but the axis names there are prone to 
interpretation, see for example the Tablet UX, which follow the original (but 
now sort-of deprecated) N900 style orientation (X for the wider axis). Note: 
This is not about portrait vs landscape UI - this is about linking the 
readings with physical device positions. Thoughts ? 

See also:
http://bugreports.qt.nokia.com/browse/QTMOBILITY-1073
http://bugreports.qt.nokia.com/browse/QTMOBILITY-1044

Best regards,
Attila Csipa
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
http://wiki.meego.com/Mailing_list_guidelines
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
http://wiki.meego.com/Mailing_list_guidelines

Reply via email to