Re: [Gimp-developer] brush tool artefacts => slow brush tools

2010-10-10 Thread Sven Neumann
On Sun, 2010-10-10 at 17:24 +0200, Olivier wrote: > There are no longer brush tool artefacts on the canvas, which is very > good. Unfortunately, and maybe this is because of the repair, the > brush tools are now very slow. Olivier, please, this is ongoing development. And yes, we are using the app

Re: [Gimp-developer] Detecting "closure" of selection

2010-10-10 Thread Sven Neumann
On Sun, 2010-10-10 at 14:55 +0200, Ofnuts wrote: > > (let ((count (cdddr (gimp-histogram (car (gimp-image-get-selection image)) > > HISTOGRAM-VALUE > > 255 > > 255 > > (= (car

Re: [Gimp-developer] brush tool artefacts => slow brush tools

2010-10-10 Thread Martin Nordholts
On 10/10/2010 05:24 PM, Olivier wrote: > There are no longer brush tool artefacts on the canvas, which is very > good. Unfortunately, and maybe this is because of the repair, the brush > tools are now very slow. Hi Oliver This is known, the bug report for it is: Bug 631766 - Bad performance when

[Gimp-developer] brush tool artefacts => slow brush tools

2010-10-10 Thread Olivier
There are no longer brush tool artefacts on the canvas, which is very good. Unfortunately, and maybe this is because of the repair, the brush tools are now very slow. On a computer with an Intel Core i5 processor and with a small image, say 640x480, the problem is not visible. With a large image,

Re: [Gimp-developer] Detecting "closure" of selection

2010-10-10 Thread Ofnuts
On 10/10/2010 04:01, saulgo...@flashingtwelve.brickfilms.com wrote: > Quoting Ofnuts: > >> Is there a practical, fast way, to detect this case, i.e, that the >> selection covers the whole layer (or image?) and that no pixels remain >> unselected? I assume that inverting the selection again and te