Bug 447756 - Activity pager in vertical panel doesn't adjust its height
Summary: Activity pager in vertical panel doesn't adjust its height
Status: RESOLVED DUPLICATE of bug 348792
Alias: None
Product: plasmashell
Classification: Plasma
Component: Pager widget (show other bugs)
Version: master
Platform: Other Linux
: NOR normal
Target Milestone: 1.0
Assignee: Eike Hein
URL:
Keywords: usability
Depends on:
Blocks:
 
Reported: 2021-12-31 23:44 UTC by Matt
Modified: 2023-04-11 20:33 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Example of pager bug (47.62 KB, image/png)
2021-12-31 23:44 UTC, Matt
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Matt 2021-12-31 23:44:08 UTC
Created attachment 145000 [details]
Example of pager bug

SUMMARY
Using an activity pager with a vertical panel results in the pager becoming tiny (as it scales to panel width) instead of adjusting its height.


STEPS TO REPRODUCE
1. Create a vertical panel
2. Have at least 3 activities
3. Add an activity pager to the panel

OBSERVED RESULT
Activity pager becomes small and unusable due to scaling with panel width

EXPECTED RESULT
Activity pager should extend further down the panel and adjust its height instead of width

SOFTWARE/OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: 5.23.4
KDE Frameworks Version: 5.89.0
Qt Version: 5.15.2
Kernel Version: 5.15.12-arch1-1 (64-bit)
Graphics Platform: X11

ADDITIONAL INFORMATION
This also happens with the virtual desktops pager, I might make a separate issue about that as well
Comment 1 Nate Graham 2023-04-11 20:30:29 UTC
The pager keeps the aspect ratio of the desktop arrangement. 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 2 Nate Graham 2023-04-11 20:33:23 UTC

*** This bug has been marked as a duplicate of bug 348792 ***