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

List:       kde-core-devel
Subject:    Re: Kded and DBus
From:       Daniel Nicoletti <dantti12 () gmail ! com>
Date:       2013-01-03 22:29:17
Message-ID: CACo8zOek7gPp2kCPFhnrWP=meLok5Nvpf4XwS15NQ9ebWdfz-g () mail ! gmail ! com
[Download RAW message or body]

Can't you move the code to a different thread?
 Em 03/01/2013 20:03, "C=E9dric Bellegarde" <gnumdk@gmail.com> escreveu:

> Le jeudi 3 janvier 2013 18:09:25 David Edmundson a =E9crit :
> > Always use async calls for everything
>
> On kded-appmenu part, the blocking code isn't in kded-module but in
> appmenu-qt
> plugin used to export the menu over dbus:
>
> http://bazaar.launchpad.net/~indicator-applet-developers/appmenu-
> qt/trunk/view/head:/src/appmenuplatformmenubar.cpp#L406
>
> QDBusInterface host(REGISTRAR_SERVICE, REGISTRAR_PATH, REGISTRAR_IFACE)
> call
> dbus_connection_send_with_reply_and_block () to do the dbus introspection=
.
>
> If someone know how to bypass this issue...
>
> regards,
> --
> C=E9dric
>

[Attachment #3 (text/html)]

<p>Can&#39;t you move the code to a different thread?<br>
</p>
<div class="gmail_quote">Em 03/01/2013 20:03, &quot;Cédric Bellegarde&quot; &lt;<a \
href="mailto:gnumdk@gmail.com">gnumdk@gmail.com</a>&gt; escreveu:<br type="attribution"><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> Le jeudi 3 \
janvier 2013 18:09:25 David Edmundson a écrit :<br> &gt; Always use async calls for everything<br>
<br>
On kded-appmenu part, the blocking code isn&#39;t in kded-module but in appmenu-qt<br>
plugin used to export the menu over dbus:<br>
<br>
<a href="http://bazaar.launchpad.net/~indicator-applet-developers/appmenu-
qt/trunk/view/head:/src/appmenuplatformmenubar.cpp#L406" \
target="_blank">http://bazaar.launchpad.net/~indicator-applet-developers/appmenu-<br> \
qt/trunk/view/head:/src/appmenuplatformmenubar.cpp#L406</a><br> <br>
QDBusInterface host(REGISTRAR_SERVICE, REGISTRAR_PATH, REGISTRAR_IFACE) call<br>
dbus_connection_send_with_reply_and_block () to do the dbus introspection.<br>
<br>
If someone know how to bypass this issue...<br>
<br>
regards,<br>
--<br>
Cédric<br>
</blockquote></div>



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