Bug 162553 - plasmoids order not remembered in resized panels
Summary: plasmoids order not remembered in resized panels
Status: RESOLVED FIXED
Alias: None
Product: plasma4
Classification: Plasma
Component: panel (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-05-24 12:24 UTC by mangus
Modified: 2008-06-16 01:12 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments
screenshot (12.51 KB, image/png)
2008-05-29 12:36 UTC, richlv
Details

Note You need to log in before you can comment on or make changes to this bug.
Description mangus 2008-05-24 12:24:46 UTC
Version:           trunk (using Devel)
Installed from:    Compiled sources
Compiler:          gcc (GCC) 4.3.0  

Starting from scratch, if  I configure a panel with some plasmoids in it and then I resize the panel then quit the session , on restart panel is not resized and plasmoids order is messed up.
Comment 1 mangus 2008-05-24 14:22:44 UTC
I found that maybe the traditional menu plasmoid have problems.
I prefer use two different traditional menus in the panel , adding another one, or simply removing the default then adding it again , makes the menu appear on the right side of the panel, while I placed it on the left side , before restarting a session. HTH
Comment 2 richlv 2008-05-29 12:36:17 UTC
Created attachment 24991 [details]
screenshot

i might be seeing the same behaviour.
4.1 beta, opensuse livecd.
default panel. if i open 'panel settings' and resize it shorter, then back,
widgets are not placed in the same places as they were - for example, systray
goes to the left of the clock etc. sometimes widgets even cover eachother - see
the screenshot.
Comment 3 richlv 2008-05-29 12:43:02 UTC
further testing seems to indicate that this seems to be only systray related and easy to reproduce if panel is resized quickly.
i have no idea whether it is a different issue, though, so i won't file a new report for now.
Comment 4 Aaron J. Seigo 2008-06-16 01:12:48 UTC
*** Bug has been marked as fixed ***.