Den 2016-04-24 kl. 10:32, skrev Murray Cumming:
Also, if we add signal::block()/unblock() then any object's signals
can be blocked/unblocked even if you don't want to offer that ability.
That breaks encapsulation, letting client code interfere with the
internal logic of the class. glib's signals allow this, and it is
quite often abused. This leads to fragile hacky code, because the
author of the code that emits the signal never meant to offer that
interface or make any promise about its behaviour.
There are signal_base::block()/unblock() methods, but they don't do what
James Lin wants them to do. They iterate over all connected slots and
set or unset the slots' blocking state.
Kjell
_______________________________________________
libsigc-list mailing list
libsigc-list@gnome.org
https://mail.gnome.org/mailman/listinfo/libsigc-list