Well, till now I only used the diskussed approach for resolving url data from vimeo or youtube , as these are not included in the fast keys and at least vimeo had a blocking call in libquvi.
Regarding the operation cancelation I also tried to run grl_browse in a seperate thread with a new GMainContext, and it worked except the gdata libe under grl-youtube made trouble from time to time. Not on cancelation , but on next browsing after a cancelation. Just I have no time right now to get deeper into this. Anyway it would be nice to have a solution to let grilo run in a seperate thread outside of the default main context. If I have news I will report Roland On 28.05.2013, at 10:33, Bastien Nocera wrote: On Tue, 2013-05-28 at 10:17 +0200, Roland Peffer wrote: > Thats not correct! It is. > I really digged into it. > If I for example search on the vimeo plugin, a curl blocking function > in libquvi gets called after a while. It's not g_idle_*, it's the callback... > and that locks the main context for a while. > So if I use a main context running on another thread the problem is > solved. > To do so we need to add that modifications. The modifications are a hack. Implement async look up properly. _______________________________________________ grilo-list mailing list [email protected] https://mail.gnome.org/mailman/listinfo/grilo-list
