Summary: | REGRESSION: The icons don't ignore autohide panels | ||
---|---|---|---|
Product: | [Unmaintained] kdesktop | Reporter: | Maxilys <maxilys> |
Component: | icons | Assignee: | Benoit Walter <b.walter> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | normal | CC: | aseigo, des, faure, finex, kollix, tyrerj |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: |
Screen shot with KDE-3.4
Screen shot with KDE-3.5 Area where icons can be placed panels unhidden Panels unhidden (2) |
Description
Maxilys
2005-11-17 15:13:13 UTC
Created attachment 13813 [details]
Screen shot with KDE-3.4
This is my desktop as configured with KDE-3.4.x.
Created attachment 13814 [details]
Screen shot with KDE-3.5
This is what I got when I upgraded to KDE-3.5.
There is a hidden panel at the top, upper left, and right bottom, in addition
to the visible clock and a hidden taskbar in the lower left.
I can confirm that this is still the case with the 3.5.0 release Comments on the dot seem to minimize this so I am adding two more screen shots. The first one shows with yellow cross hatching the area where I can place icons on my DeskTop. It is NOT possible to place icons anywhere outside of this area. The second one shows the panels unhidden. Created attachment 13831 [details]
Area where icons can be placed
Created attachment 13832 [details]
panels unhidden
Created attachment 13898 [details]
Panels unhidden (2)
Someone suggested that the bug was the panel in the middle of the screen. This
is not the case. Reordering the panels and the left top panel is on the edge
of the screen, but the problem still exists.
More bad news. Every time I start this test desktop, the desktop icons are rearranged. I can conform this bug. I use an external, 40px wide autohidden taskbar in the top-left corner of the screen. All my desktop icons are now moved 400 px to the right everytime I log in. :-( This worked flawlessly in KDE 3.4 and is a rather annoying regression. :-( Ups, typo: Well, the external taskbar's width is set to 400px of course, not 40px, sorry. I can also confirm this bug on 3.5.0. I have a panel at the top (not autohide) and a panel on the bottom (which is auto-hidden). I also have "Align to Grid" turned on. When kdesktop starts, it initially positions the icons correctly (i.e. the way they were when I logged out). Then when kicker starts and sets up its panels (both of which are initially shown, before the bottom one hides itself almost immediately), kdesktop rearranges the icons. (Generally, icons that are further down get moved up or pushed to the right.) It looks like commit 444012 is the cause of this regression. Perhaps it was a design error.
IAC, it needs to be changed back to the way it used to be. This new "feature":
<<
Kicker now has the capability to tell kdesktop an area to place desktop icons in. This area is different from the workArea (which is used by windows/the window manager). The desktopIconsArea is not modified when a panel/extension is hidden/shown - only when a new panel/extension is created or an existing one is moved.
>>
doesn't work. Autohide panels shouldn't take up destop space. They SHOULD cover icons when they are unhidden. If some do not want that to occur then it needs to be configureable.
This problem appears to have been fixed in 3.5.2. There is another problem and I will file a new bug for that. Bug closed. Kdesktop is no more mantained. First, we don't close bugs, we resolve them. Second, this has not been fixed. @James: is this a valid issue for KDE 4 too? Anyway, why even this bug was marked as fixed ?????? There is one other thing. I do not know if this is a KDesktop or Kicker bug since it is the interaction of these two apps that doesn't function correctly. Fortunatly this seems being only a KDE 3 bug, KDE 4 doesn't suffer of this problem. About this bug on KDE3, I don't know if it is a kicker or a kdesktop bug. Anymore, kicker seems no more mantained too, but (atm) is not officially "unmantained". So I'm leaving this opened even if it will not probably fixed (imho) ;-( kicker is just as unmaintained as kdesktop, let's not waste time about whether to keep a report open or not if the related codebase is dead. |