Hi again David,
On Friday, 6 July 2012, David Buchan wrote:
When the user presses a button, an idle function is begun to watch a flag
which will tell it a message has been left in a string for it by a worker
thread. The worker thread is then started. It will produce results to be
Hi John,
Thanks for taking the time to provide such a great answer. I REALLY appreciate
it.
I need to investigate semaphores more, but in the mean time, I'd like to try
the first solution you gave (hopefully tonight or tomorrow). I have a question
though.
If I understand the first solution
On 6 July 2012 14:49, David Buchan pdbuc...@yahoo.com wrote:
If I understand the first solution correctly, we're creating a separate idle
function for each message. If the worker thread gets a bit ahead of the GUI
updates, then a few idle functions might pile up. ok. But one thing I don't
Wow!
Absolutely fantastic.
Thanks again John.
Dave
From: jcup...@gmail.com jcup...@gmail.com
To: David Buchan pdbuc...@yahoo.com
Cc: gtk-app-devel-list list gtk-app-devel-list@gnome.org
Sent: Friday, July 6, 2012 10:16 AM
Subject: Re: yet another thread
hi!
i'm trying to create a custom signal for a file-selection-button, code
is here: http://bpaste.net/show/DZwtKCPDBcpCv0g0NQCn/
the problem:
when the signal is emitted in the image_selection-method, it doesn't
call the connected signal handler, if this handler is not within the
same class. but
Hi Moritz,
A good thing to do would be to pair your example down into something
runnable from a console without any dependencies except GObject and Gtk if
possible. Anyone helping will have to do this anyway in order to observe
the problem. However, something that immediately stuck out in the
