Steve McClure wrote:

On Thu, 2004-08-26 at 14:09, Danny Milosavljevic wrote:


Hi,

Am Donnerstag, den 26.08.2004, 14:47 +0300 schrieb Nikos Kouremenos:


toggle.set_active( False )
toggle.stop_emission('toggled') # doesn't work


- Connect the signal only after you called set_active
- Set a flag that you check in your callbacks



If you are connecting the signal manually, that is, outside of glade,
such that you have a handle to the signal handler as returned by the
toggle.connect() call, you can:


toggle.signal_handler_block(mytogglebuttonhandler)
toggle.set_active(False)
toggle.signal_handler_unblock(mytogglebuttonhander)




Yeah I fristly though about having a flag. then I was curious why stop_emission doesn't work [and how one should use it and work ok]

the .signal_handler_block/unblock is cool and what I wanted [also mentioned in 3.1 {but 3.2 example doesn't make use of it}]
anyways
in gtk2 it's not signal_handler_block/ublock but handler_block/ublock


and I thank you for your help :)


and just because someone said why I want this.. I'm writing an GNOME panel applet, where I make use of this code. http://members.hellug.gr/nkour/dcapplet/ _______________________________________________ pygtk mailing list [EMAIL PROTECTED] http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/

Reply via email to