On Sunday 21 March 2010, Steve Fryatt wrote: > Just for completeness, the issue here seems to be that the various > _initialise() functions for the treeview modules (cookies_initialise(), > etc) need be called from gui_init2() after the content fetchers have been > set up. When called from gui_init(), as they were in the RISC OS > front-end, the content system can't fetch the graphics that early in the > process and so flags them all up as having errors. > > Given that I don't fully understand the browser core yet, does this > explanation sound vaguely sane or have I just stumbled across a fix by > accident?
Yes, that looks like the reason. See netsurf_init() in desktop/netsurf.c for the order of things during initialization. I've started documenting what each front end function should do at http://wiki.netsurf-browser.org/Documentation/Front_end_functions I don't have any particular knowledge of this. I'm just doing it by reading the code. Please feel free to add to it. James -- James Bursa, NetSurf developer http://www.netsurf-browser.org/
