widget's signal callback: inside gdk lock?

Hi, I wonder if the callback function I connect to a widget's signal (like toggled signal of a checkbutton) is already inside the gdk lock--or if I have to take care of gdk_threads_enter/leave with any code inside this callback function? Felix -- 5 GB Mailbox, 50 FreeSMS

Re: widget's signal callback: inside gdk lock?

Fe Kater wrote: Hi, I wonder if the callback function I connect to a widget's signal (like toggled signal of a checkbutton) is already inside the gdk lock--or if I have to take care of gdk_threads_enter/leave with any code inside this callback function? Since signals are run synchronously

Re: widget's signal callback: inside gdk lock?

Felix Kater wrote: [...] a. The lock is already aquired by gtk when the button is toggled by the user's mouse click--so the callback is already (automatically) inside the lock from the client programmer's view. b. The lock has to be aquired explicitly by the client programmer who is using gtk

Re: widget's signal callback: inside gdk lock?

On 9/19/05, Tristan Van Berkom [EMAIL PROTECTED] wrote: Fe Kater wrote: Hi, I wonder if the callback function I connect to a widget's signal (like toggled signal of a checkbutton) is already inside the gdk lock--or if I have to take care of gdk_threads_enter/leave with any code inside