Bug 116322 - pixmaps on buttons and kicker shrink on mouse over
Summary: pixmaps on buttons and kicker shrink on mouse over
Status: RESOLVED DUPLICATE of bug 113235
Alias: None
Product: kicker
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Aaron J. Seigo
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-11-14 08:18 UTC by Michi
Modified: 2005-12-01 18:15 UTC (History)
0 users

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


Attachments
to get an idea (17.94 KB, image/png)
2005-11-14 08:29 UTC, Michi
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Michi 2005-11-14 08:18:47 UTC
Version:            (using KDE 3.5 (RC1) Level "a" , SUSE 10.0 UNSUPPORTED)
Compiler:          Target: i586-suse-linux
OS:                Linux (i686) release 2.6.13-rc6-git13-4-default

it's just a guess that it has to do with the pixmaps really, and has only occured since the 3.5 versions, at least from alpha release on.
The thing that happens is that in kicker, when having activated a background image, hovering over some portion with a button, let's say the kmenu button or any other link to an application on the panel, the background tile shrinks into the top left corner, having 34x40px (plus minus).
Similar thing happens when using a style like ThinKeramik, which I guess uses that pixmap background; when hovering over some pushbutton, it sometimes does not draw the whole button background but only the leftmost portion, the rest stays "flat". Sometimes here means that you have to press the left mouse button first anywhere apart from the pushbutton and then hover over it. That said, I just realised that's the same with kicker. So maybe it has also to do with some dirty mouse event?

Hope that was enough description

bye M;chi
Comment 1 Michi 2005-11-14 08:29:17 UTC
Created attachment 13432 [details]
to get an idea
Comment 2 Aaron J. Seigo 2005-12-01 18:15:43 UTC

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