Bug 166017

Summary: Two pager plasmoids should have different configs
Product: [Unmaintained] plasma4 Reporter: Thomas Zander <zander>
Component: generalAssignee: Plasma Bugs List <plasma-bugs>
Status: RESOLVED DUPLICATE    
Severity: normal CC: aseigo, lucas
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Compiled Sources   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Thomas Zander 2008-07-08 10:46:32 UTC 
Version:            (using Devel)
Installed from:    Compiled sources

To reproduce;
insert a pager on your horizontal panel. The default settings are fine.
Insert another pager somewhere on your screen.  Make it 100x500 pixels in size.
Now change the configuration of the second pager.  If you have 4 desktops, make it show 4 rows, if you have 8 desktops make it show 8 rows.  In other words, one desktop per row.

Call kquitapp plasma to cleanly shut down plasma and then start it again.

What I see is that *both* pager plasmoids have one desktop per row.  I expected the two plasmoids to have separate configuration persistency so the pager on my horizontal panel would have been 1 row and the second pager would have been 8 rows tall.
ps. size is persisted correctly, this is about the pager configuration only.
Comment 1 Aaron J. Seigo 2008-07-08 12:18:37 UTC 
actually, pager config affects how the window manager lays out the virtual desktops (for things like keyboard shortcuts). so while they used to have their own config, this led to inconsistency with the window manager interaction.

the problem is that changing the global config in one applet doesn't inform other instances of the same applet, so you can change settings temporarily, and when you start up again they then update to the new shared configuration.

so... technically this bug is the latter problem.
Comment 2 lucas 2008-07-08 12:57:27 UTC 
There is a junior job at bug 105779 to separate the layout from the pager if anyone feels like doing it.
Comment 3 Aaron J. Seigo 2008-11-10 09:20:28 UTC 

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