#175: libpurple API called from different threads
-----------------------+----------------------------------------------------
Reporter: cavedon | Owner: vadim
Type: defect | Status: reopened
Priority: critical | Milestone: QuteCom 2.2-RC4
Component: misc | Version: 2.2
Resolution: | Keywords:
Field_os: all |
-----------------------+----------------------------------------------------
Comment(by cavedon):
Replying to [comment:6 nikita]:
> Hello, to fix http://trac.qutecom.org/ticket/173 we have merged the two
eventloop under linux when it's possible (Qt configured to use glib
eventloop).
Mhm, there are at least 3 event loops in qutecom
* Qt event loop (for the GUI)
* Model even loop (based on boost thread and implemented in
owutil/thread), run by the WengoPhone class
* libpurple glib-based event loop
In order to fix this issue we need to merge the libpurple loop with the
*model* loop.
Actually merging the GUI loop with the libpurple loop, wouldn't it worsen
the user experience, as the GUI might get blocked by libpurple operations?
(apart from breaking the Model-View-Controller paradigm...)
> I will try your patch as soon as possible.
Thanks.
PS: of course if the model & libpurple threads get merged, than my patch,
as well as changeset [519] should no longer be needed.
--
Ticket URL: <http://trac.qutecom.org/ticket/175#comment:7>
QuteCom <http://trac.qutecom.org>
_______________________________________________
QuteCom-dev mailing list
[email protected]
http://lists.qutecom.org/mailman/listinfo/qutecom-dev
