RSS/Atom feed Twitter
Site is read-only, email is disabled
  1. Chat
  2. Useful links
  3. Polls

Featured content

Suspending display update

This discussion is connected to the gimp-developer-list.gnome.org mailing list which is provided by the GIMP developers and not related to gimpusers.com.

This is a read-only list on gimpusers.com so this discussion thread is read-only, too.

5 of 5 messages available
Toggle history

Please log in to manage your subscriptions.
Suspending display update Ofnuts 14 Jun 08:08
  Suspending display update Rob Antonishen 14 Jun 11:11
   Suspending display update Joao S. O. Bueno 14 Jun 12:05
   Suspending display update Ofnuts 14 Jun 20:28
    Suspending display update Joao S. O. Bueno 15 Jun 00:45
Ofnuts
2012-06-14 08:08:39 UTC (over 12 years ago)

Suspending display update

I have a python plugin that does very many bucket-fills (potentially several thousands) on small selections. While it runs I see the selections in the image window (but curiously, not the painting), and the painting on the layer thumbnail in the layers list. I assume theses display update take a significant amount of CPU and the script could run faster without them? Is there some way to suspend these updates or is the only technique to duplicate everything in a display-less image and copy back the result?

Rob Antonishen
2012-06-14 11:11:33 UTC (over 12 years ago)

Suspending display update

There are no pdb calls to change the view settings. I've always duplicated the image and worked on the duplicate without it being displayed. Also disable the undo stack of this duplicate to save memory.

-Rob A > ------------------------------
*From:* "Ofnuts"
*To:* "gimp-developer-list@gnome.org" *Sent:* June 14, 2012 4:08 AM
*Subject:* [Gimp-developer] Suspending display update

I have a python plugin that does very many bucket-fills (potentially several thousands) on small selections. While it runs I see the selections in the image window (but curiously, not the painting), and the painting on the layer thumbnail in the layers list. I assume theses display update take a significant amount of CPU and the script could run faster without them? Is there some way to suspend these updates or is the only technique to duplicate everything in a display-less image and copy back the result?

Joao S. O. Bueno
2012-06-14 12:05:56 UTC (over 12 years ago)

Suspending display update

On 14 June 2012 08:11, Rob Antonishen wrote:

There are no pdb calls to change the view settings.  I've always duplicated the image and worked on the duplicate without it being displayed.  Also disable the undo stack of this duplicate to save memory.

Indeed - I also have found this to be effective. Disabling the undo stack on the duplicate image save not only memory, but makes it quite faster as well.

js
->

-Rob A >
________________________________
From: "Ofnuts"
To: "gimp-developer-list@gnome.org" Sent: June 14, 2012 4:08 AM
Subject: [Gimp-developer] Suspending display update

I have a python plugin that does very many bucket-fills (potentially several thousands) on small selections. While it runs I see the selections in the image window (but curiously, not the painting), and the painting on the layer thumbnail in the layers list. I assume theses display update take a significant amount of CPU and the script could run faster without them? Is there some way to suspend these updates or is the only technique to duplicate everything in a display-less image and copy back the result?
_______________________________________________ gimp-developer-list mailing list
gimp-developer-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-developer-list

_______________________________________________ gimp-developer-list mailing list
gimp-developer-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-developer-list

Ofnuts
2012-06-14 20:28:10 UTC (over 12 years ago)

Suspending display update

On 06/14/2012 11:11 AM, Rob Antonishen wrote:

There are no pdb calls to change the view settings. I've always duplicated the image and worked on the duplicate without it being displayed. Also disable the undo stack of this duplicate to save memory.

OK, thanks, will try that... I've got the undo thing covered already.

Joao S. O. Bueno
2012-06-15 00:45:43 UTC (over 12 years ago)

Suspending display update

On 14 June 2012 17:28, Ofnuts wrote:

On 06/14/2012 11:11 AM, Rob Antonishen wrote:

There are no pdb calls to change the view settings.  I've always duplicated the image and worked on the duplicate without it being displayed.  Also disable the undo stack of this duplicate to save memory.

OK, thanks, will try that... I've got the undo thing covered already.

Yes - but beware that if you do that on your actual work image, undo will broken for it thereafter. Disabling the undo system on a new image (gimp-image-undo-disable) can make things really faster.

js ->