Bug 74513

Summary: placement of kicker and panels
Product: [Unmaintained] kicker Reporter: michael mastrangelo <mmastran>
Component: multiscreenAssignee: John Firebaugh <jfirebaugh>
Status: RESOLVED DUPLICATE    
Severity: normal CC: opensource
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: RedHat Enterprise Linux   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: snap shot illustrating problem that occurs (1 monitor only)

Description michael mastrangelo 2004-02-07 21:18:40 UTC 
Version:            (using KDE KDE 3.2.0)
Installed from:    RedHat RPMs

I use dual monitors and put 1 panel on 1 screen and another on another but they will not both lay flat on the bottom of my two screens. 

If I have 2 panels on 1 screen (one 30% located on the bottom justified left and one 30% located on the bottom justified right) they also do not both ly flat on the bottom

What I want is the "Tetris effect" where if there is room below, they should fall :-)
Comment 1 Hugo Costelha 2004-04-29 19:18:52 UTC 
Hi,

I think this is important also for the case when we have two panels in one screen and want to put one aside the other.

Hugo
Comment 2 michael mastrangelo 2004-04-29 20:21:32 UTC 
Created attachment 5817 [details]
snap shot illustrating problem that occurs (1 monitor only)

This illustrates that the problem in fact occurs with only 1 monitor.
Comment 3 Hugo Costelha 2004-04-30 12:06:28 UTC 
One way to go around it is to change the behaveour of the panels to allow them to be covered by other windows.

This means that this is really a bug. When the panels are small enough to be one aside the other without covering one another, they do not get one aside the other unless we change the coverability option. But that's weird since they didn't cover each other.
Comment 4 Mathieu Jobin 2004-08-31 19:26:17 UTC 
as in 3.3, this bug can be closed
Comment 5 Mathieu Jobin 2004-08-31 19:33:32 UTC 
sorry, this is not fixed... only with xinerama, with two different screens.
however, i think it can be considered duplicate of bug #51423
Comment 6 Aaron J. Seigo 2004-09-15 00:49:00 UTC 

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