[PATCH] KProcess port of khelpcenter
Ralf Habacker
ralf.habacker at freenet.de
Sun Dec 16 22:33:32 GMT 2007
Oswald Buddenhagen schrieb:
> On Sun, Dec 16, 2007 at 09:49:27PM +0100, Ralf Habacker wrote:
>
>> a major problem of porting K3Process to KProcess is that KProcess does not
>> provide a pointer to the K3Process in the exit signal.
>>
>>
> if you want to be lazy, use sender() in the slot.
>
This looks the easiest way and will make porting much easier.
>> Another issue is the multibyte handling described in
>> http://techbase.kde.org/Development/Tutorials/Common_Programming_Mistakes#Reading_QString_from_a_KProcess.
>>
>> Wouldn't it be better to implement specific signals in KProcess or a
>> subclass to avoid that this has to be fixed on every place where KProcess
>> is needed ?
>>
>>
> i considered it, but given that the qtextstream approach is going to
> work with qt 4.4, i'm not sure we should add it in 4.1.
>
>
I understand, thanks.
Ralf
More information about the kde-core-devel
mailing list