(trying to remember) Because I assumed there is never any boolean feedback on a resize operation and so GTK would be correct in assuming resize must always succeed.
However I now realize the correct feedback method is in the form of resize events (which, sheepishly, I authored), so yeah GTK can check if the resize succeeded. You're right GTK should be open here too. Even if a tiling/stage WM fails to honour the requested size, the toolkit should be listening for resize events and respond to the fact that it is now tiled. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtubuntu in Ubuntu. https://bugs.launchpad.net/bugs/1670390 Title: Desktop applications don't get properly resized when launched in staged mode Status in Canonical System Image: In Progress Status in QtMir: In Progress Status in gtk+3.0 package in Ubuntu: New Status in qtmir package in Ubuntu: In Progress Status in qtubuntu package in Ubuntu: Invalid Status in unity8 package in Ubuntu: In Progress Bug description: Steps to reproduce the issue: 1 - Put unity8 in staged mode 2 - Launch a desktop application like kate or qtcreator Expected outcome: The launched application takes up the entire stage area Actual outcome: The launched application starts with some windowed size it wanted to have, not filling the entire stage area. As if launched in desktop mode. Comments: Leaving staged mode and going back into it again gets the application to resize correctly and fill the entire stage area. Going from desktop to staged mode while the desktop application is already running also works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1670390/+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
