New Tiled Data Manager ideas and tests

[Dmitry Kazakov]

>
> It's a bug. The next time a user calls
>> KisTileReadWriteProcessor::setupProcessor() or
>> KisTileReadWriteProcessor::KisTileReadWriteProcessor() with different args
>> and then calls copyData, dataIdx won't be set to the correct value.
>>
>
> =)
> It's done purposely to test this speed boost. More than that with current
> test-suite it works fine as applyProcessor calls setupProcessor() with the
> same data-pointer all the times. I know it's dirty hack, but, all the same,
> i'm going to change processors' interface now.
>

Ben:
Well.. You were right... =(


-- 
Dmitry Kazakov
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.kde.org/pipermail/kimageshop/attachments/20090604/96354b41/attachment.htm