QtConcurrent mask procession - proof of concept

[David REVOY]

Thanks a lot Boud and Sven for the help and the how-to. Unfortunately, 
the patch return me :
> deevad at deevad ~/koffice/koffice-build/krita/plugins/paintops/libbrush 
> $ patch -p0 < ~/qtconcurrentmask.diff
> patching file kis_auto_brush.cpp
> Hunk #1 FAILED at 22.
> Hunk #2 FAILED at 34.
> Hunk #3 FAILED at 201.
> Hunk #4 FAILED at 254.
> 4 out of 4 hunks FAILED -- saving rejects to file kis_auto_brush.cpp.rej
> deevad at deevad ~/koffice/koffice-build/krita/plugins/paintops/libbrush $
But maybe this is too complicated for my user level to dive into , and I 
prefer here to follow the advice of Sven ;
> Keep in mind that is just a performance experiment and not suited for 
> regular painting yet as the brush can show come artifacts.
I will not waste your time in asking you things about my patch/code/etc 
noob level skill ... :) Compiling and running will be my personal 
frontier; and keep feedback and test. I will not keep the bad usage to 
say my bug and complains in the mailing list or IRC too ; I will use the 
bugtracker tool.

:) https://bugs.kde.org/show_bug.cgi?id=255031

-David

On 10/23/2010 10:08 AM, Boudewijn Rempt wrote:
> On Saturday 23 October 2010, David REVOY wrote:
>    
>>> Maybe you have an i7
>>>        
>> Yep, a fresh one :) ( 870 )  I'm highly interrested in all works done
>> about performance . How to apply a patch ? (surely it something
>> obviously simple for a developper, but I prefer to ask a link to a good
>> and compatible doc before 'google it' )
>>
>>      
> * Make sure your checkout of Krita trunk is completely up to date
> * save sven's patch to your home directory
> * go to koffice/krita/plugins/paintops/libbrush
> * execude this command in that directory: "patch -p0<  ~/qtconcurrentmask.diff"
>
> then make and install as usual. For added responsiveness, build in kritadevs mode, not the default debug mode. This is a switch for cmake: -DCMAKE_BUILD_TYPE=KritaDevs
>
> Something like:
>
> cmake $srcFolder -DCMAKE_INSTALL_PREFIX=/home/boud/kde/inst -DKDE4_BUILD_TESTS=TRUE -DHAVE_MEMORY_LEAK_TRACKER=FALSE -DCMAKE_BUILD_TYPE=KritaDevs
>
> Now I noticed from your screenshot that you have almost all debug messages enabled. If you find and install an application called "kdebugdialog" (I am not sure where in *buntu or mint that is) you can run that, check the "disable all debug output" checkbox and press ok.
>
>