Bug 177211 - KCategorizedView assumes all categories to have the same height
Summary: KCategorizedView assumes all categories to have the same height
Status: RESOLVED FIXED
Alias: None
Product: kdelibs
Classification: Frameworks and Libraries
Component: kdeui (show other bugs)
Version: SVN
Platform: Compiled Sources All
: NOR normal
Target Milestone: ---
Assignee: kdelibs bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-12-08 10:50 UTC by Christoph Keller
Modified: 2009-12-14 17:43 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christoph Keller 2008-12-08 10:50:03 UTC
Version:            (using Devel)
Compiler:          vc++ 2008 
OS:                MS Windows
Installed from:    Compiled sources

KCategorizedView overpaints items/categories when KCategoryDrawer::categoryHeight() returns different heights.

I tried to add more spacing between the categories, so the first category returns the real height and all following ones add 20 pixels. So the second category is drawn on the right place but the first item of it is drawn like the categoryHeight() was the first category.

I did not test this on other systems than windows.
Comment 1 Rafael Fernández López 2008-12-08 23:34:29 UTC
KCategorizedView is being rewritten from scratch for the implementation of my dreams. It is almost finished. It will make it for 4.3.

It is happening on http://repo.or.cz/w/personal-kdelibs.git?a=blob;f=kdeui/itemviews/kcategorizedview.cpp;h=6a05d2641092004f3ffdaf51d3917b348b9eb0d6;hb=categorizedView

At this very moment since I went for a real scratch implementation, it is binary incompatible. I will work later on the binary compatibility issues.

This problem should be solved with the new implementation, and yes, it was a bug on the previous one.
Comment 2 Christoph Feck 2009-12-09 06:44:58 UTC
Rafael, does your new implementation fix this issue? If yes, please resolve as FIXED.
Comment 3 Rafael Fernández López 2009-12-14 17:43:31 UTC
Yes, this has been fixed by the new implementation. Some things are still pending to be finished, but this feature in particular should work out of the box.