Bug 218363 - slide out widgets in a top panel remain partially visible when sliding in again
Summary: slide out widgets in a top panel remain partially visible when sliding in again
Status: RESOLVED DUPLICATE of bug 218291
Alias: None
Product: plasma4
Classification: Unmaintained
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-12-12 10:11 UTC by Christophe Olinger
Modified: 2009-12-12 15:07 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christophe Olinger 2009-12-12 10:11:56 UTC
Version:            (using Devel)
OS:                Linux
Installed from:    Compiled sources

I like having my panel at the top screen edge. I realized that all widgets that use a sliding animation (lancelot, device notifier, panel settings, new add widget) remain partially visible after they slide out of the screen again (in this case up). Items with fade in animations (kmix, klipper) do not have this problem. When the panel is at the bottom edge, the problem is not apparent. The remaining parts disapper again when a refresh is triggered.
I also tried a vertical panel, no problems there.
Comment 1 Beat Wolf 2009-12-12 10:17:19 UTC
could this be a kwin problem?
Comment 2 Christophe Olinger 2009-12-12 11:39:08 UTC
I guess the sliding animations are calculated for blottom panels. When I change the height of the panel, the remaing part size aso changes. Its roughly always 90% of the panel size
Comment 3 Christophe Olinger 2009-12-12 12:04:46 UTC
Here an image
http://imagebin.ca/view/Yz4QR3.html
Comment 4 Marco Martin 2009-12-12 15:06:13 UTC
is the piece of visible window "usable" or it's just garbage painted?
i.e if you click on it does it disappear?
i really think it's kwin related
Comment 5 Marco Martin 2009-12-12 15:07:38 UTC

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