09/04/17 ROM breaks Screen config/Netsurf
Frederick Bambrough (1372) 837 posts |
Open a Netsurf window. Open Configuration – Screen. Move Netsurf window and enjoy the fireworks. Haven’t checked any other app windows yet. Edit: Seems to be just Netsurf. Tried Fireworkz, OPro, Pipedream, StrongEd, Zap & LaBella all of which seem OK. |
Doug Webb (190) 1180 posts |
Frederick What version of Netsurf is that with and also what versions of support modules that it requires have you installed. Also I assume you have updated your disc image as well? |
Frederick Bambrough (1372) 837 posts |
Disc image is today’s. Netsurf is 3.7 (Dev C1 #4059). Support modules; AcornURI 0.26, Iconv 0.12, SharedUnixLibrary 1.14, Tinct 0.14 What’s happening is that |
Chris Gransden (337) 1207 posts |
On a Titanium after running Configuration→Screen the NetSurf window goes ’Fireworks. Changing the mode to the current mode gets things back to normal or pressing F12, Return the desktop screen mode changes to 640×480 in 2 colours. |
Frederick Bambrough (1372) 837 posts |
Screen resolution here is 1024×768, the max & native for this Dell 1505FP. Beagleboard -xM. |
Steve Pampling (1551) 8170 posts |
Try without the use of Tinct1 by selecting OS based dither in the netsurf image handling config. 1 May be irrelevant but I do recall strange things happening with Tinct use on releases a few years ago. |
Jeffrey Lee (213) 6048 posts |
The Wimp probably needs fixing so that it will only refresh currentmode on Service_ModeFileChange if the desktop hasn’t been entered yet. currentmode is directly exposed by Wimp_ReadSysInfo 1 (it’s supposed to be the current Wimp mode), so once you’re in the desktop it should only really change on when an actual (Wimp) mode change occurs. |
Frederick Bambrough (1372) 837 posts |
Already selected. |
Sprow (202) 1158 posts |
Wouldn’t it be simpler to only refresh it when the task count changes from 0 to 1? I assume (though can’t actually see the line) it’s a call to Wimp_Initialise that triggers the initial mode change, in response to the *Desktop command starting a Wimp task. Then there’d be no need to bother reading it when the module initialises, nor on Service_Reset, nor on Service_ModeFileChange. But since I can’t see where the initial mode changes by just staring at it, I’ve no doubt missed something subtle and would need to stick a breakpoint in to see what’s going on. |
Jeffrey Lee (213) 6048 posts |
Use the The main place to worry about is Wimp_SetMode / *WimpMode. If the wimp isn’t active yet then it won’t actually trigger a mode change; all it will do is update currentmode, thereby selecting the screen mode that should be used when the Wimp does get entered. The boot sequence relies on this behaviour – the Configure.Monitor file is located in PreDesk. |
Frederick Bambrough (1372) 837 posts |
Just to confirm, today’s ROM (11/12 Apr) has resolved the problem on this BB -xM. |
John Williams (567) 768 posts |
I would like to congratulate whoever fixed this, and ask that the revisions page actually says who is responsible for updates – not to criticise failures, but to congratulate fixes for bugs and so forth. Too often it says just ROOL, and the individual is anonymised. I want to be able to say “Thank you, whoever!” |
Chris Evans (457) 1614 posts |
I agree with your comment. |