Signals: Is this the expected behaviour of connect() ?

[Thiago Macieira]

Eduardo Robles Elvira wrote:
>And indeed, it seems that signals were designed somehow  to be only
> triggered by it's owner (and friends & parents).  You cannot do emit
> new
>A()->signalA(); inside B. It doesn't even compile because the signal
>is "protected". But then, as the given code shows, connecting signalB()
> to signalA() and triggering signalA(), works fine - so maybe this is a
> bug?

No.

Signal to signal connection is allowed and part of the design.

-- 
  Thiago Macieira  -  thiago (AT) macieira.info - thiago (AT) kde.org
    PGP/GPG: 0x6EF45358; fingerprint:
    E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20080225/460e507d/attachment.sig>