Bug 159394 - Panel height changes after plasma restart
Summary: Panel height changes after plasma restart
Status: RESOLVED FIXED
Alias: None
Product: plasma4
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
: 159773 (view as bug list)
Depends on:
Blocks:
 
Reported: 2008-03-16 10:31 UTC by Petri Damstén
Modified: 2008-03-24 06:48 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Petri Damstén 2008-03-16 10:31:19 UTC
Version:            (using Devel)
Installed from:    Compiled sources
OS:                Linux

Two horizontal panels grow when plasma is restarted. Originally:
http://kotisivu.lumonetti.fi/damu0/images/desktop.jpg
After restart:
http://kotisivu.lumonetti.fi/damu0/images/desktop_after_restart.jpg

Vertical panel seems to keep it's size.
Comment 1 Michael Olbrich 2008-03-16 13:22:33 UTC
The problem is that the panel has its own ideas about size and does not save this. The default is "normal" size, which is why your vertical panel keeps its size.

I'm not sure how to fix this. We could save the panel size but that would be redundant. The containment stores the geometry already.
Unfortunately Containment::location() and Containment::geometry() are not available during Panel::init().
plasma experts: Is there a reason why corona calls init() before loadConstraints()?
Comment 2 Bart Cerneels 2008-03-19 10:51:30 UTC
I can confirm this bug in the most recent SVN at this moment (r787420).
Might I add that this is very annoying.
Comment 3 Andrew Lake 2008-03-19 17:23:13 UTC
Confirmed in my recent svn build (not at my computer but it's no more than a week old).  Has been that way for a while for me.
Comment 4 Chani 2008-03-22 22:56:29 UTC
whoops, forgot there was a report for this. fixed in revision 788869
Comment 5 Chani 2008-03-24 06:48:58 UTC
*** Bug 159773 has been marked as a duplicate of this bug. ***