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

List:       kde-devel
Subject:    Re: KIO: Synchronous wrapper over Async and more
From:       Nikhil Marathe <nsm.nikhil () gmail ! com>
Date:       2010-03-12 16:39:50
Message-ID: e1dff1921003120827j8c3583ds4966281fa329ba25 () mail ! gmail ! com
[Download RAW message or body]

On Thu, Mar 11, 2010 at 11:28 PM, David Faure <faure@kde.org> wrote:
> On Wednesday 10 March 2010, Nikhil Marathe wrote:
>>   loop.exec(); // block the loop ( see
>> http://www.erata.net/qt-boost/synchronous-http-request/ )
>
> See the trash ioslave for an example of nested event loops
> in a slave.
> kdebase/runtime/kioslave/trash/kio_trash.cpp, enterLoop()
>
> You definitely need a QCoreApplication in kdemain(), it was missing in
> your code sample.
>
> However, receiving DBUS invocations/signals might not work,
> I'm not too sure about that. Hmm, this -is- about dbus calls, or am I
> wrong?

Thanks a lot, its fixed. I was adding excess complexity. It wasn't about DBUS
calls, just normal slots

>
>> In addition my debug statements don't work, I see KIO debug
>> output, but not the one specific to my slave.
>
> kioslaves are started by kdeinit, so their debug output goes to
> ~/.xsession-errors on most setups. Alternatively, type "kdeinit4"
> in a terminal to restart it there, and then load your kioslave,
> its output will go to that terminal.
>

Thanks for this tip. It helped me learn that if I declare SIGNAL(
function( arg ) )
then arg should be a fully qualified name even if I have a 'using
namespace ...' directive.

Regards,
Nikhil
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

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