<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN" "http://www.w3.org/TR/REC-html40/strict.dtd"><html><head><meta name="qrichtext" content="1" /><style type="text/css">p, li { white-space: pre-wrap; }</style></head><body style=" font-family:'Sans Serif'; font-size:10pt; font-weight:400; font-style:normal;">Dnia Saturday 03 January 2009, Jakub Stachowski napisał:<br>
> Hello,<br>
[ ... ]<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>> Another possible optimization: for each item, KFileItemDelegate checks<br>
> actual size of file icon. Is this really necessary? Or maybe it would be<br>
> enough to check size for first icon in the view and then reuse it.<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>Some more checking shows that for given decoration size (stored in option.decorationSize), actual icon size is always the same - one of the common sizes like 64x64, 256x256 etc.<br>
Caching the size makes laying out items about 20% faster (on top of previous patch).<br>
KFileItemDelegate objects are not created in great numbers (one per view), so adding two QSize fields will not have any effect on memory usage.<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p></body></html>