I insist to use threads. If you are calling an external program you have no major problem with syncronization. If the machine has only one processor it could be better to make that system() inside a thread with less priority so your GUI will continue working without any lag.
If you wish could even use a different process where to call that program:
...
if ((pid = fork()) == 0) {
/* We're in a child process */
...
system(...);
...
}
if (pid < 0) err_sys("Fork error");
/* Parent process */
/* get back to the gtk_main() loop */
PD: About threads, take a look at:
http://developer.gnome.org/doc/API/glib/glib-threads.html
Esteban Quijano Vincenzi
Artinsoft corp.
Phone: ++(506) 283-3144
Fax: (506) 283-2655
e-mail: [EMAIL PROTECTED] <[EMAIL PROTECTED] >
-----Original Message-----
From: Andrej Prsa [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, July 18, 2001 12:29 AM
To: [EMAIL PROTECTED]
Subject: Re: Screen updates while long time running subroutine
Hello!
> okay, but my earlier post ("picking up resize events") has the sizing of the drawables in terms of the gdkwindow size IN the main routine.
>
> so that's not much help, really ..
> Anyone???
I'm only going to rephrase the question: what would happen if you have to deal with an external binary program you call with system(), which takes long time to execute? Is there a way to update the GUI-related stuff?
Andrej
_______________________________________________
gtk-list mailing list
[EMAIL PROTECTED]
http://mail.gnome.org/mailman/listinfo/gtk-list
