Re: signals and copy constructors



>
>No, I am not. I am confusing it with the signature of the underlying
>(C level) signal, which always includes the emitting GObject.

there is no underlying C-level signal to a SigC++ signal unless its a
SigC++ signal that is used to notify about C-level signals. perhaps
that is what you meant. sorry if this appears pedantic.

--p



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