[PATCH] KProcess port of khelpcenter

Andreas Pakulat apaku at gmx.de
Thu Dec 20 19:51:47 GMT 2007

On 20.12.07 20:14:16, Ralf Habacker wrote:
> Oswald Buddenhagen schrieb:
>> On Thu, Dec 20, 2007 at 06:59:37PM +0100, Ralf Habacker wrote:
>>> you probably mean [...]
>>> no problem here :-)
>> you are looking into the apidoc of the wrong class. ;)
> i see, you mean this
>    meinproc->setOutputChannelMode(KProcess::SeparateChannels);
> This is a bit irritating because in the former I used QProcess and have  
> learned a different behavior. It is partial not really clear when to use 
> KProcess and when QProcess like the following case:

Whenever there's API in KProcess to do something use it, else use
QProcess API. Isn't that hard, IMHO - and the same with all KXXX stuff
that has a QXXX base class.

> To be able to handle the finished signal i have to use QProcess related 
> types in the signal definition like
>    connect( meinproc, SIGNAL( finished( int, QProcess::ExitStatus) ),
>             this, SLOT( meinprocExited( int, QProcess::ExitStatus) ) );

I'd always use this, KProcess has no enumeration named ExitStatus.


All the troubles you have will pass away very quickly.

More information about the kde-core-devel mailing list