Hi hi, That part with the 'calculation' was a lie ;-). My project is about interface renderers. One renderer uses gtk for it's interfaces. Other renderers are text (with speech-output and braile-friendly layout), phone (via capi) and opengl (via coin-3d). The system has a remote control console (implemented as a thread with a tiny webserver). With a browser you can connect to the application and change adaption parameters. Therewith you can exchange the used renderer as well. This finished the main-loop, then temporary shuts down all dialogs, switches to the new renderer, reopens the dialogs and starts the new main-loops. Anyway many thanks for helping. Stefan Gus Koppel wrote:
Stefan Kost wrote:many thanks for the reply. I found a solution. I am bound to finishing the event-loop earlier. Therefore now I do gtk_widget_destroy(GTK_WIDGET(window)); if(!gtk_main_level()) { while(gtk_events_pending()) gtk_main_iteration_do(FALSE); }I tend to ask why you're bound to finishing the event loop earlier? I also tend to suggest not to finish the main loop at all if you're going for lengthy calculations afterwards, as you mentioned earlier. How about visualizing progress and offering the user a choice to abort, adjust or restart the process? _______________________________________________ gtk-app-devel-list mailing list gtk-app-devel-list gnome org http://mail.gnome.org/mailman/listinfo/gtk-app-devel-list
-- http://gitk.sourceforge.net
Attachment:
kost.vcf
Description: Vcard