Hi Igor,
On Tuesday, 3 July 2012, Igor Chetverovod wrote
Hi David,
probably you should use macros:
gdk_threads_enter ()
gdk_threads_leave ().
Those macros were used to lock the main gdk thread in earlier versions of
gtk if you wanted to call gtk_ functions from many threads. They are now
My understanding is that child threads must never alter the UI in any way.
If I have a program which spawns a child thread to download some data and I
want to be able to have a dialog pop up should an error occur, is it correct to
say that I need an idle function to be running concurrently to
(sorry forgot list)
On 3 July 2012 01:50, David Buchan pdbuc...@yahoo.com wrote:
My understanding is that child threads must never alter the UI in any way.
If I have a program which spawns a child thread to download some data and I
want to be able to have a dialog pop up should an error
On 3 July 2012 02:10, James Morris jwm.art@gmail.com wrote:
(sorry forgot list)
On 3 July 2012 01:50, David Buchan pdbuc...@yahoo.com wrote:
My understanding is that child threads must never alter the UI in any way.
If I have a program which spawns a child thread to download some data and
yep. Seems to be working.
Thanks!
Dave
From: James Morris jwm.art@gmail.com
To: David Buchan pdbuc...@yahoo.com
Sent: Monday, July 2, 2012 9:10 PM
Subject: Re: Threads and idle functions
On 3 July 2012 01:50, David Buchan pdbuc...@yahoo.com wrote:
My
Hi David,
probably you should use macros:
gdk_threads_enter ()
gdk_threads_leave ().
Best regards,
Igor
2012/7/3, David Buchan pdbuc...@yahoo.com:
My understanding is that child threads must never alter the UI in any way.
If I have a program which spawns a child thread to download some data
