3 ms·
Often with newer UI frameworks like that used by plasma, basic interactions with familiar widgets just don't work as expected. It's the same argument levied aga
by ubercow13 7y ago
Often with newer UI frameworks like that used by plasma, basic interactions with familiar widgets just don't work as expected. It's the same argument levied against any non-native app whenever this comes up, whether it's QML or Electron or whatever.
As a concrete example, the KDE application menu will close whenever you move the cursor off of it onto another window, unlike any menu in any other desktop UI widget toolkit [1].
So from some users' perspective, things like the move to plasma can seem like little more than a series of UI regressions. The basics just don't work so well any more, and the only upside is maybe slightly prettier graphics. It can be disheartening. Here is an application menu from KDE 1 in 1999 which I am sure worked just fine [2].
[1] https://www.reddit.com/r/kde/comments/9a41si/possible_bug_application_menu_closes_when/ https://www.reddit.com/r/kde/comments/9a41si/possible_bug_ap...
[2] https://en.wikipedia.org/wiki/K_Desktop_Environment_1#/media/File:KDE_1.1.jpg https://en.wikipedia.org/wiki/K_Desktop_Environment_1#/media...
- agumonkey 7y agothis is part of it, and a too complicated layout grid it seems.
- simion314 7y agoIt seems to be a bug but for me personally Plasma is not the reason I use KDE, I love KWin and krunner and all the other applications. KWin the window manager is very configurable so I can do a lot of things with it, krunner I launch my apps with it without using the mouse, the file manager is configurable and good for my use cases, the text editor is also very decent for small and quick edits. On top of that GTK2 and GTK3 apps are integrated as much as possible. If other DE matches you needs better and if it does it by default then I am happy for you I am not trying to sell you anything.