Yes, that is correct. The client script uses 'gtk_server_callback' though, an internal GTK-server command, which, in it's turn, calls 'gtk_main_iteration()'. In this way the GTK-server binary will actually receive the callback from GTK. Only then the widgetID will be returned to the client program. If you want to return from GTK immediately, 'gtk_main_iteration_do(0)' must be used. This function is used by the NONE and UPDATE arguments of 'gtk_server_callback'. Peter Citeren Sunburned Surveyor <sunburned.surveyor@xxxxxxxxx>: > That makes some sense. I was actually reading about the > "gtk_main_iteration()" function. > > Just so I make sure that I understand correctly: > > The GTK-Server calls gtk_main_interation(), which attempts, a single time, > to "catch" a callback signal from the GUI. This is why the > "gtk_server_callback(WAIT)" function must be embedded in the loop of the > client script. We are making repeateded calls to gtk_main_iteration() in the > loop of our client script, which, in essence, simulates the GTK main loop. > > Is that correct? > > Landon > > P.S. - I'll check out that link that you forwarded. Thanks. > > -- http://www.gtk-server.org