My concerns are threefold: 1. there is no good name for this feature: "automatic" doesn't capture specific behaviour; 2. I don't understand why this specific use case needs any special support; and, 3. what advantage is expected from Mir being involved?
As discussed above: Clients can implement this behaviour right now. Toolkits can implement this behaviour right now. Involving Mir would be to give the Window Management Policy another customization point should it choose not to allow the state request made by the client. But why is that useful? -- 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: In Progress 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: In Progress 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 : [email protected] Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp

