Bug 80184 - kicker menu cut off when side pixmap is shown
Summary: kicker menu cut off when side pixmap is shown
Status: RESOLVED DUPLICATE of bug 77545
Alias: None
Product: kicker
Classification: Plasma
Component: general (show other bugs)
Version: 1.1
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: John Firebaugh
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-04-23 10:45 UTC by quin
Modified: 2004-04-23 10:56 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:

Attachments
K menu with side pixmap and "Maximum number of entries" set to 0 (40.09 KB, image/png)
2004-04-23 10:46 UTC, quin 		Details
K menu with side pixmap and "Maximum number of entries" > 0 (49.28 KB, image/png)
2004-04-23 10:46 UTC, quin 		Details
K menu without side pixmap and "Maximum number of entries" > 0 (43.03 KB, image/png)
2004-04-23 10:47 UTC, quin 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description quin 2004-04-23 10:45:02 UTC 
Version:           1.1 (using KDE 3.2.2, SuSE)
Compiler:          gcc version 3.3 20030226 (prerelease) (SuSE Linux)
OS:          Linux (i686) release 2.4.20-4GB-athlon

When both the option "Show side image" is selected and
"Maximum numer of entries" for most recently/frequently used apps is set to 1 or greater, a part of the K menu is cut off.
In fact, the part which is cut off is equal in size to the side pixmap.

If the side pixmap is deactivated, the menu is always OK, regardless of whether or not any most recently/frequently used apps are shown.
Comment 1 quin 2004-04-23 10:46:06 UTC 
Created attachment 5732 [details]
K menu with side pixmap and "Maximum number of entries" set to 0
Comment 2 quin 2004-04-23 10:46:53 UTC 
Created attachment 5733 [details]
K menu with side pixmap and "Maximum number of entries" > 0
Comment 3 quin 2004-04-23 10:47:36 UTC 
Created attachment 5734 [details]
K menu without side pixmap and "Maximum number of entries" > 0
Comment 4 Stephan Binner 2004-04-23 10:56:59 UTC 

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