<br><br><div class="gmail_quote">On Tue, Mar 16, 2010 at 4:33 PM, Boudewijn Rempt <span dir="ltr"><<a href="mailto:boud@valdyas.org">boud@valdyas.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">On Tue, 16 Mar 2010, Dmitry Kazakov wrote:<br>
<br>
> I don't think we need this.<br>
><br>
> KisTileHashTableIterator returns the number of non-default tiles, or (more<br>
> precisely) the number of preallocated tiles. After you fixed the extents<br>
> bug, these terms coincide. So this check is superfluous.<br>
<br>
</div>Isn't it so that within a rectangle of allocated tiles there can be<br>
unallocated, default pixel, tiles?<br></blockquote><div><br>What do you mean? Which rectangle? extents?<br>If they are unallocated, they are not returned by the iterator. If they are allocated, but empty (store default value), this is some subtle bug of the calling code, i guess. This can happen if we use non-const iterator for reading, or if we just direct copy data from empty device, but this is quite rare case, i think.<br>
</div></div><br><br clear="all"><br>-- <br>Dmitry Kazakov<br>