On 04/01/2011 08:45 AM, Stylianou, Costas wrote:
>  I hope someone can advise me the recommended way of doing a screen lock in 
MeeGo after using QtMobility API to detect screen orientation.

Are you asking how to trigger the lockscreen UI, or lock the orientation of 
your app (like a video player might want to force the view into landscape mode 
while playing a video clip?)

>  The latter, lock screen orientation to either landscape or portrait.

We don't do a low level xrandr rotation of the screen, so rotation totally handed inside the application or the toolkit used by the application.

So... if you have a traditional Qt application or even a QML app that isn't using a component library like meego-ux-components that automatically does scene rotations for you, then your code would have to explicitly rotate the the view (speaking generically here since this could apply to any app using who knows what UI technology) which means the concept of orientation locking would be something your code would need to implement.

We are in the process of migrating our QML based code to all use MeeGo.Components instead of MeeGo.Labs.Components since MeeGo.Components is better positioned to work correctly with qt-components, but as i now review Window i see that we seem to be missing the concept of an orientation lock that we currently have in MeeGo.Labs.Components.

Christian or Ben... is there something I am missing or do we still need to add a mechanism to lock the orientation?

In the labs version of Window I had a orientationLocked boolean property, so apps would:

scene.orientationLocked = true;
scene.orientation = someorientation;

I'm not sure if the qt-components definition of a window has some other way of dealing with this. Note that we will not be able to migrate the video player, app grid, and lockscreen till we have orientation locking supported.

    --rusty
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
http://wiki.meego.com/Mailing_list_guidelines

Reply via email to