Hello John-Mark, thanks for your explanation. Am Dienstag, den 24.08.2010, 20:09 +0200 schrieb John-Mark Bell <[email protected]>:
> The Amiga frontend is more intelligent and will block until a timeout > occurs, so it can trigger scheduled events as appropriate. That means it may not serve the next netsurf loop as fast as possible (it's still waiting for an timer event, but maybe netsurf core already would like to have control to do it's stuff...), ... this amiga solution is just an workaround, at least so it seems to me, and that's how I understand the comment. > The framebuffer frontend is more intelligent still and will block until > the time at which the next scheduled event should occur, at the latest. framebuffer, riscos, beos and gtk, they all manage an external netsurf core variable named content_reformat_pending, or some name like that. I don't keep track of pending events, because I don't queue any redraw / reformat events. Maybe I should do it before thinking about this ;) I don't understand: what has content reformat/redraw to do with further progress of the internal rendering? And I'm not really sure if this always running well within the framebuffer version. Kind regards, m
