I remain unconvinced that this needs anything to be implemented in Mir at all.
This appears to be a Qt-specific API that can be implemented entirely in the client-side QPA - the QPA needs to know whether the client wants automatic state anyway, knows the form-factor the surface is on, receives events when form-factor changes, and can set the appropriate state. Since this is a Qt-specific API it seems reasonable for the Qt-specific code to implement it. What this doesn't allow is for the shell to determine what “default” means, but given the API is just “something selects between fullscreen and windowed” it doesn't really allow the shell much lattitude anyway. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1535397 Title: [enhancement] Implement support for QWindow::visibility set to Automatic Status in The Avila project: New Status in Canonical System Image: Triaged Status in canonical-pocket-desktop: New Status in Mir: New Status in QtMir: New Status in camera-app package in Ubuntu: New Status in gallery-app package in Ubuntu: New Status in mediaplayer-app package in Ubuntu: New Status in mir package in Ubuntu: New Status in qtubuntu package in Ubuntu: Triaged Status in unity8 package in Ubuntu: Triaged Bug description: We need to support windows setting their visibility to "Automatic", when in Staged mode the window should be fullscreen, whereas in windowed, it should be a normal window. Qt API: http://doc.qt.io/qt-5/qwindow.html#Visibility-enum To manage notifications about this bug go to: https://bugs.launchpad.net/avila/+bug/1535397/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
