Re: [sigc] Deprecate signal<>::slots() ?

[Murray Cumming <murrayc murrayc com>]

On So, 2016-04-24 at 16:03 +0200, Kjell Ahlstedt wrote:
> Den 2016-04-24 kl. 15:20, skrev Murray Cumming:
> > On So, 2016-04-24 at 13:21 +0200, Kjell Ahlstedt wrote:
> > >  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.
> > Isn't that exactly what he wants?
>  I don't think so. See https://mail.gnome.org/archives/libsigc-list/2
> 016-April/msg00011.html.
> There's no 'blocked' flag in the signal itself. signal_base::block()
> won't block slots that are connected after the call to
> signal_base::block(). signal_base::unblock() unblocks all slots,
> including those that were blocked when signal_base::block() was
> called.

Ah, yes, thanks. I feel like deprecating that too, for the same
reasons, though that last issue makes this one even worse.

-- 
Murray Cumming
murrayc murrayc com
www.murrayc.com