> I'm sure I understand you because of the following, but to make
> absolutely certain... you mean: locking shared structures from within
> generic widget code (such as that defined by the GtkRadioButton) is a
> terrible idea. right? (don't bother answering this question, unless my
> head is rea
On Thu, Feb 03, 2005 at 06:54:04AM -0500, Paul Davis wrote:
...
> >I'm wondering this because I see some operations being performed on a
> >GSlist in the widget's code, and I don't see any locking taking place.
>
> Terrible idea. That should not happen. If it does, you need to
> redesign your prog
>Looking at the code of GtkRadioButton, I have to question whether it's
>thread safe. I don't use threads (yet) in my application... and
No part of GTK or any X Window toolkit is thread-safe *by
default*. You can either choose to use explicit locking functions
provided by GTK, or you can ensure
Hi.
Looking at the code of GtkRadioButton, I have to question whether it's
thread safe. I don't use threads (yet) in my application... and
there's a good chance I won't at all, and I don't really even know how
they work. (on Linux are they implemented with help from the clone()
system call?)
I
