Version: unspecified (using Devel) OS: Linux Opening the app Calligra Active, displays the app fullscreen, means hides the top bar, which is a deadlock for the user; there is no way back to "normal" UI without a hardware keyboard Reproducible: Always Steps to Reproduce: - start Calligra Active - see the topbar covered completely by the app - try to go back to your current activity -> no chance Actual Results: - see the topbar covered completely by the app Expected Results: - no app can cover the whole screen completly, if there is no arrow/whatever icon that leads back to the normal activity screen
sorry, happens on 2011-12-06-09-24-basyskom-plasma-active-testing-meego-usb-live
Fania, do you consider full screen applications a valid usecase for Plasma Active? If not I could easily block applications from going fullscreen in KWin. Personally given the design, I would say there is never a valid usecase for fullscreen windows as it is not possible to switch away from it unless the window supports it which we cannot rely on (see calligra - which forced me to power off the device)
I've aleady filed a bug in calligra active for this one (see https://bugs.kde.org/show_bug.cgi?id=288083) as I think the problem is on their part. I do see full screen applications as a valid use case. See videos for example. Playing a video fullscreen definitely does make sense. Or showing a presentation. Or an image slideshow (we already have that in the image viewer and I wouldn't want to miss it). You don't want any distracting stuff there. So pretty please do not prohibit fullscreen ;) I'd rather put in the yet-to-write HIG for Active apps that - an application may never start fullscreen - if a fullscreen mode can be activated, it has to be possible to go back to windowed mode with a button or touching anywhere on the screen So for Active apps, the blocking fullscreen mode should never happen (and in Calligra Active, it simply does not make sense unless doing a presentation, and definitely not at startup). If someone install a non-active app which can go fullscreen without any means to return without a keyboard, then it's his/her problem, not ours.
well, in gerenal I think you are correct Thomas, that fullscreen mode makes sense for a lot of apps. But as long as we cannot guarantee that they offer a way back, a touch friendly way back (!) we need to block that. For PA3 we can think of nicer and more elegant ways, like the top bar dynamically fading out and swiping back in, for example. For a hot fix and the coming release, I would prefer the offer of Martin to block it. It just happend to me again with Gwenview, where the image displayed in fullscreen created a complete deadlock.
The temporary solution: add the following to ~/.kde/share/config/kwinrulesrc: [2] Description=Disable Fullscreen fullscreen=false fullscreenrule=2 types=4294967295 wmclass=* wmclasscomplete=false wmclassmatch=0 This disables fullscreen for all windows. We could ship it either as a kconf update script or a predefined kwinrulesrc.
Already fixed. Verified on 2011-12-12-14-38-basyskom-plasma-active-devel-meego-usb-live.iso