DBus - problem with dispatch
dibo20 at wp.pl
Sat Jun 18 10:16:18 EDT 2011
Exactly. Some times ago, 500ms timer was enough to catch all pidgin signals.
Now with 500ms my timer can't see even one signal. I change interval to 50ms
and it catch ~70%. With 5ms it catch ~95% . Finally I change timer to thread
which call read_write in loop (with 1 second timeout) and it seems that it
can catch all. Maybe I leave it that. Sorry for my english
2011/6/17 Etan Reisner <deryni at pidgin.im>
> On Fri, Jun 17, 2011 at 01:45:49PM +0200, Krzysztof wrote:
> > Hi,
> > I have dbus plugin which listening for ReceivedImMsg and SentImMsg
> > I wrote it in free pascal which doesn't have dbus bindings yet so I can't
> > use such functions like "setup_with_mainloop". I use low lewel dbus api.
> > This code connect to pidgin dbus:
> <snip code>
> > And I have a timer which every 50 miliseconds call:
> > dbus_connection_read_write_dispatch(FDBConn,0);
> > All messages are handled in dbus filter method:
> <snip more code>
> > This worked well for some time. But now, I notify that it doesn't "catch"
> > all signals. I notify that after upgrade pidgin to 2.8.0. Before, even if
> > timer had 500 miliseconds interval, it catch all signals. Any idea?
> > Regards.
> What do you mean it doesn't catch all the signals? With a 50ms timer there
> are some sent/received events that your code never sees (but that doesn't
> happen with a 500ms timer)?
> Support at pidgin.im mailing list
> Want to unsubscribe? Use this link:
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Support