[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: Does the "stub" stuff work for kded modules?
From:       George Staikos <staikos () kde ! org>
Date:       2002-03-28 18:04:08
[Download RAW message or body]

On Thursday 28 March 2002 12:58, Michael Goffioul wrote:
> George Staikos wrote:
> > On Thursday 28 March 2002 11:43, Michael Goffioul wrote:
> > > I'd like to create and use a stub for my kdeprintd module (kded
> > > module). I added kdeprintd.stub to the sources, but it doesn't seem to
> > > work. Is this possible, or do I have to write the marshalling code by
> > > hand?
> >
> > IIRC, I had the same problem when working on one of my kded modules too. 
> > I could only get it to work by using kssld.skel.
>
> Maybe I misunderstood, but the skel is for the "server" side. I.e. inherits
> from KDEDModule, add a section k_dcop: in your header, and add
> <filename>.skel to the Makefile.am. I also did that for my kdeprintd
> module.
> What I'm talking about is the client side, which wants to access the kded
> module. With a normal dcop app, you can avoid to write all the mashalling
> code when calling a function in the remote app, by using a stub. Just add
> <filename>.stub to the client sources, and you get a wrapper for easy
> access to the remote app.

   Sorry I was ambiguous.  Yes, skel worked with a kded module but stub does 
not, last I checked.  It wouldn't compile for me if I tried to create a stub.  
Maybe I was doing something wrong though.

-- 

George Staikos

[prev in list] [next in list] [prev in thread] [next in thread]