Ofnuts wrote:
> On 17/04/17 12:05, Peter Suetterlin wrote:
> > I could fix the problem by selecting the full area before the call to
> > gimp-edit-copy. But acording to the docs it should do this by itself if
> > nothing is selected.
> IMHO the real fix is to use other ways to move pixels.
Hi Mitch,
Michael Natterer wrote:
> If any script works fine in 2.8, but not in git master,
> please file a bug.
OK, here: https://bugzilla.gnome.org/show_bug.cgi?id=781408
Cheers,
Pit
___
gimp-developer-list mailing list
List address:
On 17/04/17 12:05, Peter Suetterlin wrote:
I could fix the problem by selecting the full area before the call to
gimp-edit-copy. But acording to the docs it should do this by itself if
nothing is selected.
IMHO the real fix is to use other ways to move pixels. Applications
should not use the
On Mon, 2017-04-17 at 11:05 +0100, Peter Suetterlin wrote:
> Hi,
>
> I recently switched to the 2.9 series of gimp(*). Some of the
> script-fus I
> regularly use do need babysitting, in particular the 'maximize local
> contrast'
> script by Roy Johnson. I fixed the deprecated function calls,
Hi Peter,
If any script works fine in 2.8, but not in git master,
please file a bug.
Regards,
Mitch
On Mon, 2017-04-17 at 11:05 +0100, Peter Suetterlin wrote:
> Hi,
>
> I recently switched to the 2.9 series of gimp(*). Some of the
> script-fus I
> regularly use do need babysitting, in
Hi,
I recently switched to the 2.9 series of gimp(*). Some of the script-fus I
regularly use do need babysitting, in particular the 'maximize local contrast'
script by Roy Johnson. I fixed the deprecated function calls, but it always
failed in the final step where an edit buffer captured via
