On 14 June 2012 08:11, Rob Antonishen <rob.antonishen@xxxxxxxxx> 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" <ofnuts@xxxxxxxxxxx> > To: "gimp-developer-list@xxxxxxxxx" <gimp-developer-list@xxxxxxxxx> > Sent: June 14, 2012 4:08 AM > Subject: 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@xxxxxxxxx > https://mail.gnome.org/mailman/listinfo/gimp-developer-list > > > _______________________________________________ > gimp-developer-list mailing list > gimp-developer-list@xxxxxxxxx > https://mail.gnome.org/mailman/listinfo/gimp-developer-list > _______________________________________________ gimp-developer-list mailing list gimp-developer-list@xxxxxxxxx https://mail.gnome.org/mailman/listinfo/gimp-developer-list
