The API in the bug's description (QWindow::contentOrientation) is new in Qt 5.1 (which we are not using yet).
If we could use it right now, we would have to:
1) set it appropriately in the toolkit's OrientationHelper.qml
2) implement QPlatformWindow::handleContentOrientationChange in QtUbuntu so that it writes that value somewhere the keyboard can read it; for example, the xcb equivalent of QtUbuntu sets a property on the XWindow. It could be that we want the shell/window manager/compositor (= unity) to know about it too.
In the meantime, a workaround could be possible but the cost is quite high (introducing a temporary API in the toolkit that would do now what QtUbuntu would do later).
The API in the bug's description (QWindow: :contentOrienta tion) is new in Qt 5.1 (which we are not using yet). er.qml ::handleContent OrientationChan ge in QtUbuntu so that it writes that value somewhere the keyboard can read it; for example, the xcb equivalent of QtUbuntu sets a property on the XWindow. It could be that we want the shell/window manager/compositor (= unity) to know about it too.
If we could use it right now, we would have to:
1) set it appropriately in the toolkit's OrientationHelp
2) implement QPlatformWindow
In the meantime, a workaround could be possible but the cost is quite high (introducing a temporary API in the toolkit that would do now what QtUbuntu would do later).