Comment 2 for bug 1588485
Revision history for this message
| Stefano Verzegnassi (verzegnassi-stefano) wrote | #2 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
demo site
(Get the code!)
I guess ContentHub is not meant to be loaded asynchronously - at least, not yet.
There may be some issue in ContentHub, which should (could?) properly synchronize the communication between the two apps involved in the content transfer.
However, for now, it seems that DocViewer is not *fast enough* to catch the DBus signal sent from the service, so I would say there's just a bad usage of the ContentHub API inside DocViewer.
The code used here in DocViewer has been taken from address-book-app and, in this case, the async loading has been removed back in 2014.
http://
By the way, loading ContentHub synchronously should not affect startup performance that much (DocViewer launches in ~2.2 seconds), therefore we can safely use this workaround.