[Kde-bindings] Re: More dcop signal questions
Richard_Dale at tipitina.demon.co.uk
Fri Jun 10 07:46:27 UTC 2005
On Friday 10 June 2005 00:29, Chris Gow wrote:
> Richard Dale wrote:
> > On Wednesday 08 June 2005 20:41, Chris Gow wrote:
> >> 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 this?
> > It will work as a KDE::Application, but the dcop ref has the pid as part
> > of its name, for instance 'konqueror-1977', rather than just 'konqueror'
> > for a KDE::UniqueApplication
> Hmm..Ok, so using the examples, I have changed dcopsignal.rb to be
> KDE::Application and in dcopslot.rb I have changed the connect line to:
> result = slottest.connectDCOPSignal("dcopsignal-*", nil,
> "testEmitSignal(QString)", "mySlot(QString)", false)
> And dcopslot is never notified of the signal (I tried both false and true
> as the volatile flag). I've also tried replacing the nil with
> "SenderWidget". None of the combinations seem to work.
I've just been trying the same test with C++ code, and it behaves exactly the
same as the ruby code - 'dcopsignal-6678' will work in the connectDCOPSignal,
but not 'dcopsignal-*' with a wild card.
More information about the Kde-bindings