Hi Ruben,
The problem is that you may never have two process, or threads
that share the same X-connection. And this is usually not
necessary either. What you want to do is the following:
++ +---+ +--+
| X | <=> | Your gtk program | <=>
>I wanted to fork the tar process off by itself have it show in it's own window
>.
[ ... ]
>/* pid = fork();
> if(pid != 0){
> perror("We are in the child"); */
> gtk_window_new(GTK_WINDOW_TOPLEVEL);
you can't do this. the parent and child cannot share acces
Dov
Thanks for the reply. I've finally had time to get back to this problem.
It seems I'm going through some growing pains with GTK at this junction.
I took your suggestion and I tried to fork the taring process and capture
the output in a text object, in a new toplevel window. This result
The reason that the label isn't drawn is that the graphics context
isn't flushed. This may be done simply by calling gtk_flush(). But
there is a more fundemental problem with your program, and it has
to do with the concept of event driven programming. In your callback
you are doing an operation w
Hello
I'm trying to write a program which changes a label from a callback and it's not
working.
rmbackup.c
#include
#include "tarlib.h"
#include "backprog.h"
int main(int argc, char **argv){
struct s1 window1;
gtk_init(&argc, &argv);
window1 = screen1();
gtk_m
