Re: copying sigc::signals
- From: Chris Vine <chris cvine freeserve co uk>
- To: Jonathon Jongsma <jonathon quotidian org>
- Cc: gtkmm-list gnome org
- Subject: Re: copying sigc::signals
- Date: Fri, 5 Mar 2010 14:45:06 +0000
On Fri, 05 Mar 2010 08:27:07 -0600
Jonathon Jongsma <jonathon quotidian org> wrote:
> On Fri, 2010-03-05 at 10:07 +0100, Mark Roberts wrote:
> > Dear Jonner et al
> > > When you copy a signal, any slots that you connect to the copied
> > > signal will also be triggered when you emit the original signal.
> > If this is so, I would expect it to work the other way round as
> > well. Does it? If (after the copy) I connect a slot to the original
> > signal, will it be triggered when I emit the copied signal?
> > Mark
> Yes, it works both ways. All copies of a sigc::signal object share
> the same slot registration table, so any changes to one will affect
> all others.
It is worse than that: a sigc::signal object does not have any one slot
registration table (well it does, but that is for its sigc::connection
objects rather than its slots). Registration with trackables is at
the slot rather than the signal level.
] [Thread Prev