New process, use g_spawn_with_pipes (or how is it called) and just pass
it through pipe.
On 11/24/2010 02:35 PM, Champ Clark III [Softwink] wrote:
On Wed, Nov 24, 2010 at 03:22:56PM +0200, Dov Grobgeld wrote:
If all you want is a popup, then you might as well create a new process
instead of a
On Wed, Nov 24, 2010 at 03:22:56PM +0200, Dov Grobgeld wrote:
> If all you want is a popup, then you might as well create a new process
> instead of a new thread. There is no advantage of using a thread as it does
> not seem like you want to pass any info between the window and the
> monitoring loo
If all you want is a popup, then you might as well create a new process
instead of a new thread. There is no advantage of using a thread as it does
not seem like you want to pass any info between the window and the
monitoring loop. Further, the way you described it, if more than one event
occurs, t
GTK is not smart toolkit and is unable to work without X display and is
not even able to reconnect to different display (or to the same later)
when the connection get lost. This is with all X based toolkits I know
of - it just seems easier for developers to just call exit() then to
install like
Hello all!
I have a multi-threaded application written in C that I'm a
bit stumped on. It's not the 'multithreaded' portion of the code I'm
having issues with. That seems to be functional. It's the GTK error
and warning handling.
The application is constantly proce
