Bug 348792 - KDE Plasma5 Pager does not adjust to the size of the panel in the vertical mode
Summary: KDE Plasma5 Pager does not adjust to the size of the panel in the vertical mode
Status: RESOLVED INTENTIONAL
Alias: None
Product: plasmashell
Classification: Plasma
Component: Pager (show other bugs)
Version: 5.3.0
Platform: Kubuntu Linux
: NOR normal
Target Milestone: 1.0
Assignee: kdelibs bugs
URL: https://youtu.be/pnk8p7gKtvA?t=32s
Keywords: usability
: 356987 444236 447756 (view as bug list)
Depends on:
Blocks:
 
Reported: 2015-06-06 19:20 UTC by kamesh
Modified: 2023-04-11 20:33 UTC (History)
13 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Showing decent height for virtual desktop pager in Plasma 5.18.5 (34.53 KB, image/png)
2021-10-26 03:45 UTC, chimak111
Details

Note You need to log in before you can comment on or make changes to this bug.
Description kamesh 2015-06-06 19:20:45 UTC
I am on: 
Kubuntu: 15.04 
KDE Plasma Version: 5.3.0 
QT version: 5.4.1 
Kernel Version: 3.19.0-16-generic 
OS Type: 64 bit




Reproducible: Always

Steps to Reproduce:
1. Create a panel in the vertical mode
2. Add the pager 
3. Adjust it as shown in the video attached. 


Expected Results:  
Should adjust automatically to the size of the panel
Comment 1 Thomas Braxton 2015-06-08 00:21:39 UTC
I think what you are seeing is on purpose. I think the pager is aspect ratio constrained, so it doesn't fill the width of the panel when the height is too small.

And you should change the product to: plasmashell component: Pager
to make sure the plasma team sees this.
Comment 2 kamesh 2015-06-08 11:25:17 UTC
The pager was not aspect ratio constrained in its previous incarnation. If it now, then it is a downgrade. I used to make a sdesk (search google images if you don't know what it is) like panel before upgrading to plasma5. Now, I cannot. 

I have now changed the product to plasmashell component: Pager. Thank you.
Comment 3 Marco Martin 2015-06-23 22:18:28 UTC
seems to work fine in master, can somebody else reproduce?
Comment 4 kamesh 2015-10-22 23:22:54 UTC
Well, I do not understand what a master is. But the bug is still there in Kubuntu 15.10 which was released today (22-10-15). That means, I am using 

KDE plasma version 5.4.2, 
Qt version: 5.4.2, 
Kernel version: 4.2.0-16-generic

Is the master version greater than KDE plasma version 5.4.2?
Comment 5 Alexander Mentyu 2018-02-21 14:00:47 UTC
Can reproduce this bug in:

Plasma: 5.12.1
Apps: 17.12.2
Frameworks: 5.43.0
Qt: 5.10.1
Kernel: 4.14.20-2-MANJARO
OS: Netrunner Rolling
Comment 6 Nate Graham 2021-08-17 16:01:51 UTC
*** Bug 356987 has been marked as a duplicate of this bug. ***
Comment 7 Nate Graham 2021-10-25 22:11:37 UTC
*** Bug 444236 has been marked as a duplicate of this bug. ***
Comment 8 chimak111 2021-10-26 03:43:53 UTC
Could this be a regression? I'm trying to attach an image of what I see with:
Operating System: Kubuntu 20.04
KDE Plasma Version: 5.18.5
KDE Frameworks Version: 5.68.0
Qt Version: 5.12.8
Kernel Version: 5.4.0-89-generic
OS Type: 64-bit
Processors: 8 × Intel® Core™ i5-10210U CPU @ 1.60GHz
Memory: 7.6 GiB of RAM

So at least for the most basic usage (single monitor, a couple of desktops), the height is decent.
Comment 9 chimak111 2021-10-26 03:45:11 UTC
Created attachment 142887 [details]
Showing decent height for virtual desktop pager in Plasma 5.18.5
Comment 10 Nate Graham 2023-04-11 20:33:17 UTC
As others have mentioned, this is intentional because the pager keeps the aspect ratio of the desktop arrangement. If it didn't do this, the desktops would get stretched vertically and look ugly and someone else would complain that it looks bad and doesn't match the actual aspect ratios of the desktops in the desktop layout anymore.

If you have a narrow vertical panel and a wide desktop layout, there's not really a sensible way for this to be any better. In general if you want your pager to make better use of the space on a vertical panel, taller-than-wide desktop layouts work better.
Comment 11 Nate Graham 2023-04-11 20:33:23 UTC
*** Bug 447756 has been marked as a duplicate of this bug. ***