Bug 189883

Summary: Panel should remember maximise setting
Product: [Unmaintained] plasma4 Reporter: Salvador I. Gonzalez <sgonzalez>
Component: panelAssignee: Plasma Bugs List <plasma-bugs>
Status: RESOLVED DUPLICATE    
Severity: wishlist CC: ach, contact, gregor, ojo, p.r.worrall, sgonzalez
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Gentoo Packages   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Salvador I. Gonzalez 2009-04-17 15:47:47 UTC 
Version:            (using KDE 4.2.1)
Compiler:          gcc (Gentoo 4.3.2-r3 p1.6, pie-10.1.5) 4.3.2 
OS:                Linux
Installed from:    Gentoo Packages

I sync my home directory between multiple computers, with differing screen resolutions.  When I login/logout/sync on a computer with a lower resolution, and then do the same on a computer with a higher resolution, the panel width starts as the width of the lower resolution screen (1024.)

When attempting to reproduce this behavior with KRandRTray, I found that the panel behaves correctly.

I think that if a user clicks the 'maximize panel' option, it should remember this setting between sessions and always attempt take up the full screen width regardless of resolution, which currently is the behavior displayed by 'regular' maximized windows.
Comment 1 Achim Bohnet 2011-04-08 12:21:04 UTC 
Still in KDE SC 4.6.2 (Kubuntu Natty)

IMO instead of a maximise button,   there should be the option 'Maximise', next to 'Left' 'Centre' and 'Right' in Panel Alignment.

A related (duplicate?) bug is https://bugs.kde.org/show_bug.cgi?id=247205 which triggers the 
panel-does-not-maximise bug is the more common situation of a laptop with external display.
Comment 2 Gregor Tätzner 2011-12-02 21:14:08 UTC 
*** Bug 247205 has been marked as a duplicate of this bug. ***
Comment 3 Gregor Tätzner 2011-12-02 21:17:50 UTC 
*** Bug 277019 has been marked as a duplicate of this bug. ***
Comment 4 Gregor Tätzner 2011-12-02 21:28:00 UTC 
its all the same

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