Version: (using KDE 4.4.0) Installed from: openSUSE RPMs I'm having a hard time finding out which desktop is active when I look at the Plasma Pager widget (see screenshot here to see what I mean -- in each picture, a different desktop is activated: [URL=http://www.imagebam.com/image/b79ed070289042/][IMG]http://thumbnails27.imagebam.com/7029/b79ed070289042.gif[/IMG][/URL] In the screenshot, I'm using the openSUSE Air theme; I've experimented with different ones, but the problem remains the same.) Part of the reason for this problem is likely the lack of consistency with regard to coloring / marking the active desktop. It would be nice if the Pager could make it clearer which the active desktop is, for example by coloring it, or encircling it, with a color that stands out more (bright red / blue / green?)
Sorry, it seems that the link to the screenshot is not working. Please try this one: http://www.imagebam.com/image/b79ed070289042/
I agree with homoludens. It's very hard to tell which desktop is active. His screenshot shows this. And it's worse when (1) each desktop has a few windows, or (2) when one window is sticky. I'm using the Oxygen theme.
Agree, using Air here. The indication of the current desktop is only a larger, brighter highlight, and I can't recognise it at a glance. The obvious presentation would be consistent with the task manager's presentation of the focussed window by using a strongly contrasting shade.
*** This bug has been confirmed by popular vote. ***
Hello! This feature request was filed for KDE Plasma 4, which reached end-of-support status in August 2015. KDE Plasma 5's desktop shell has been almost completely rewritten for better performance and usability, so it is likely that this feature request is already implemented in Plasma 5, or is no longer applicable. Accordingly, we hope you understand why we must close this feature request. If the requested feature is still desired but not implemented in KDE Plasma 5.12 or later, please feel free to open a new ticket in the "plasmashell" product after reading https://community.kde.org/Get_Involved/Bug_Reporting If you would like to get involved in KDE's bug triaging effort so that future mass bug closes like this are less likely, please read https://community.kde.org/Get_Involved#Bug_Triaging Thanks for your understanding! Nate Graham