Re: [gtkmm] Possible bug in SigC::Connection::disconnect()



>I've investigated this issue a little further now, and I think I see
>what's wrong. I'm not sure if the way I'm using the libsigc++ library is
>correct. What I do, basically, is connect a slot to a signal. When this
>signal is emitted, the slot is called, and from there I disconnect the
>current slot [from the signal] and connect another one. Now, I suspect
>this might no be legal? Maybe it should be mentioned in the
>documentation if that's the case? Any ideas anyone?

no, you can't change connections from within a signal handler, at
least not in the older version of sigc++. defer that work till later
(if working with gtkmm, use an idle handler, for example).

--p



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]