As can be seen in the picture, the pager widget has too small buttons, when used as a panel applet. It is hard to select one of the desktops with the mouse and it is impossible to see any information that might be displayed in the buttons (windows, names, etc) Reproducible: Always Steps to Reproduce: 1. Make a vertical panel (or drag the default panel to the left or right border) 2. Add the pager widget to the panel 3. Change the settings to a common (?) 3x3 virtual desktop layout Actual Results: Buttons in the pager widget are too small to contain useful information. Aspect ratio of the buttons is disadvantageous for vertical panel use. Expected Results: Two things might help: 1) Force square aspect ratio for the pager buttons -> More area per button. In my opinion mirroring the aspect ratio of the actual desktop does not enhance the user experience. 2) Reduce spacing/padding for the buttons, when used as panel applet. In a situation like this where space is already limited, those generous margins are just wasting it. This problem is probably less severe on setups with just 2x2 virtual desktops, but it will be much more severe on setups with any more than 3x3 desktops.
also with only four desktops the pager in vertical panel is useless, I noted that instead of adding pager widget to an empty panel, I use a default panel, created in horizontal and dragged in vertical position, pager place the desktops quite well, but it is not permanent, if plasma crashes the vertical panel comes back as if pager widget is added to an empty panel. I tried also to assign four rows to the pager widget in vertical panel, but the number of rows is a global setting for all the pager widgets, so you will get a bad situation in the horizontal panel. One things might help: to have the number of rows as an individual setting for each pager and not a global setting.
Hello! This bug report 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 bug is already resolved in Plasma 5. Accordingly, we hope you understand why we must close this bug report. If the issue described here is still present 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