After loading qml viewer you can press CTRL+Shift+R to force the autorotation.

Another good option is to use qt creator 2.1 to create a simple wrapper around your qml application or just a generic “viewer” that will load any qml file.

You have to tell your main.qml to resize the actual window size matching the orientation.

Maybe the runtime [doc.qt.nokia.com] object would help you for that.

Thanks for the replies. CTRL+Shift+R did the trick.

I am using

Glad to hear. It is probably a good idea to file a bug report if there is none.

fcrochik: A bug report about what? I think I am missing the issue in this post:-(

Tobias Hunger wrote:

fcrochik: A bug report about what? I think I am missing the issue in this post:-(

That changing the orientation to portrait on the qml viewer running on the n900 does not have any effect.

If you create a C++ or Python wrapper for your QML app, you can use the Maemo 5-specific attributes “Qt::WA_Maemo5PortraitOrientation” and “Qt::WA_Maemo5AutoOrientation” on your QWidget (e.g. QDeclarativeView or QMainWindow), as described in this example:

http://gutenberg.troll.no/qt-maemo-4.7/maemo5-rotation.html

This way, you don’t have to press Ctrl+Shift+R every time you start your application and you can force portrait-only mode if you want (Ctrl+Shift+R only enables auto-rotation). Obviously, this only applies if you are writing a small C++/Python wrapper and load your QML file in a QDeclarativeView, and not if you are only using the QML Viewer.

fcrochik wrote:

Tobias Hunger wrote:

fcrochik: A bug report about what? I think I am missing the issue in this post:-(

That changing the orientation to portrait on the qml viewer running on the n900 does not have any effect.

In this case the window resizes properly right. So how is this a bug?

Does it? It doesn’t on my n900 and I assume it didn’t for Tommi either or he would not have started this thread.

fcrochik wrote:

Does it? It doesn’t on my n900 and I assume it didn’t for Tommi either or he would not have started this thread.

Report a bugs on bugs.maemo.org then on the package and post instructions on how to reliably reproduce the error :) (I guess the Maemo build of qmlviewer has a special component on bugs.maemo.org, but it could be the normal Qt bugtracker as well)

@thp: That was my suggestion to the author of this thread (with not so much detail I have to say… thanks for that)