RSS/Atom feed Twitter
Site is read-only, email is disabled

Gimp internal loop

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.

2 of 2 messages available
Toggle history

Please log in to manage your subscriptions.

Gimp internal loop Radhwan Ben Madhkour 05 Aug 16:39
  Gimp internal loop Martin Nordholts 05 Aug 18:29
Radhwan Ben Madhkour
2009-08-05 16:39:05 UTC (over 15 years ago)

Gimp internal loop

Hi,

I want two persons to work on the "same" image at the same time but on different pc.

Since my last post ("tile update" on Thursday 30 July), I have had some results. One person can open Gimp, start to draw and the changes are sent to multiple pc (by multicast) and showed. This is very helpful for people who want to project a huge image on a huge screen by multiple projectors (multipexed).

The next step is to connect to gimp (or more) together.

Does anybody know where is the principal loop of gimp? (I mean where gimp is waiting for an event)

Thanks,

Radhwan

Martin Nordholts
2009-08-05 18:29:47 UTC (over 15 years ago)

Gimp internal loop

On 08/05/2009 04:39 PM, Radhwan Ben Madhkour wrote:

Hi,

I want two persons to work on the "same" image at the same time but on different pc.

Since my last post ("tile update" on Thursday 30 July), I have had some results. One person can open Gimp, start to draw and the changes are sent to multiple pc (by multicast) and showed. This is very helpful for people who want to project a huge image on a huge screen by multiple projectors (multipexed).

Since we are going to migrate to GEGL, you might want to look into IPC sharing of GeglBuffers. That would be a topic for the gegl-developer mailing list though.

Does anybody know where is the principal loop of gimp? (I mean where gimp is waiting for an event)

GIMP uses the GLib main loop library. The actual loop is entered through the call to g_main_loop_run() in app/app.c.

A general tip: You could easily find this by setting a breakpoint in basically any part of the code, trigger it, and look at the backtrace in a debugger.

BR,
Martin