[Kde-bindings] More dcop signal questions

Chris Gow sniffy at rogers.com
Wed Jun 8 18:41:50 UTC 2005


So I'm still trying to get my head around dcop signals. These may be
korundum specific or KDE dcop signals as a whole (I'm learning both :).

Anyways on with my questions (all of my questions are based on the examples
provided in examples/dcop):

1. How come dcopslot.rb has to be started after dcopsignal.rb? If I reverse
the starting order or restart dcopsignal, the doit( ) slot in dcopslot is
never called.

2. Why does dcopsignal need to be a KDE::UniqueApplication in order for the
signal/slot mechanism to work? I would like dcopslot to listen to all
instances of dcopsignal. How would I go about configuring dcopslot to do

3. In the documentation for dcop signals on the KDE developer site, I should
be able to connect a slot to any signal with the following line (this is
C++): connectDCOPSignal(0, 0, "clientDied(pid_t)", "clientDied(pid_t)",
false); can I do something similar in korundum? (related to 2 above)

That's it for now. I'll probably have more questions later :)


-- chris

More information about the Kde-bindings mailing list