On 2013-08-30 22:02:03, Marwan Tanager wrote: > On Fri, Aug 30, 2013 at 01:37:00PM +0200, Sebastian Ramacher wrote: > > On 2013-08-08 20:43:12, Sebastian Ramacher wrote: > > > There are of course other ways to fix this. One of them would be to > > > abort the rendering of the page if it becomes invisible and leaves the > > > cache. However, implementing the necessary message passing for this is > > > less trivial than just exposing this one function to check if a page is > > > cached or not. > > > > I'm currently working on a different render infrastructure in the > > features/renderer-take-2 branch. The setup is currently the following: > > > > - There is a ZathuraRenderer object that renders a page in a separate > > thread. > > - Every page widget holds a ZathuraRenderRequest object to manage > > render requests. Widgets use this object to request a page to be > > renderer and can also abort an request. > > - ZathuraRenderRequest emits a signal as soon as the page is ready. > > This sounds very cool! Nice work, Sebastian. > > > There are somethings that are not done yet. The sorting of the render > > requests is currently broken. > > I'm going to have a look at those rough edges at the nearest opportunity > (unless, of course, you reached there first!).
The sorting should work again. > > In the end I hope it's enough to cancel pending requests in the caching > > code and remove the workaround again. > > Yes, once the infrastructure is in place, this is going to be a matter of a > trivial check. Great work, man. > > > -- > Marwan > _______________________________________________ > zathura mailing list > zathura@lists.pwmt.org > http://lists.pwmt.org/mailman/listinfo/zathura -- Sebastian Ramacher _______________________________________________ zathura mailing list zathura@lists.pwmt.org http://lists.pwmt.org/mailman/listinfo/zathura
