Bug 181229

Summary:	option to autoadapt panel size when screen with higher resolution is attached
Product:	[Unmaintained] plasma4	Reporter:	m.wege
Component:	containment-panel	Assignee:	Plasma Bugs List <plasma-bugs>
Status:	RESOLVED DUPLICATE
Severity:	wishlist	CC:	aseigo, aspotashev, benni, morten, tomek
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Compiled Sources
OS:	Unspecified
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description m.wege 2009-01-18 20:30:49 UTC

Version:            (using Devel)
Installed from:    Compiled sources

I have a second screen which I attach to my laptop. This screen has a higher resolution. Unfortunately the size of the panel does not adapt and just covers 2/3 of the screen. I would be cool if there was an option to let the panel size autoadapt to the screen resolution.

Comment 1 Tomasz Kępczyński 2009-02-20 07:03:50 UTC

I can confirm this behaviour. Previous version (KDE 3.5) used to behave as requested in this wish - panel resized every time screen size changed and spanned full screen width.
This is also a problem for me but for different reason - I use my account at least from two different machines and they have screens with different resolutions. Every time I move from smaller to larger screen I have to resize.
By the way - I noticed minimum and maximum panel size in KDE4.2 but regardless of their settings - the panel size is always set to minimum. What's the purpose then?

Comment 2 Morten Schmidt 2009-09-08 10:31:31 UTC

I too can confirm this.

I use a docking station at work, and the internal monitor at home...

Booting on internal monitor, shutting down, booting using dock and external monitor, makes the panel width the size of my internal monitor...

Comment 3 Benni Hill 2011-01-29 00:23:25 UTC

I can confirm this on KDE 4.6. And even more annoying: When I switch to an external monitor with less horizontal resolution the panel still remains larger than the screen width.

Comment 4 Benni Hill 2011-02-04 19:57:24 UTC

This seems to be a duplicate of Bug 209962.

Comment 5 Aaron J. Seigo 2011-02-04 21:09:42 UTC

this actually does work; there is/was a bug in 4.6.0, hopefully that's address for 4.6.1. we'll see.

Comment 6 Alexander Potashev 2011-06-26 07:50:46 UTC


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