diff options
author | Chris Young <chris@unsatisfactorysoftware.co.uk> | 2012-02-24 20:00:51 +0000 |
---|---|---|
committer | Chris Young <chris@unsatisfactorysoftware.co.uk> | 2012-02-24 20:00:51 +0000 |
commit | b517cf331aeb2616e216b1a78cc20d0027b4e0b6 (patch) | |
tree | 9c983336568331c5356b3b0d16afdc5204b9314f /content | |
parent | 9478f0182887b119ccd08cce059c5e09b5f23d8f (diff) | |
download | netsurf-b517cf331aeb2616e216b1a78cc20d0027b4e0b6.tar.gz netsurf-b517cf331aeb2616e216b1a78cc20d0027b4e0b6.tar.bz2 |
option_screen_compositing to enable switching compositing for NetSurf's own
screen on/off.
Some experimentation with compositing and simple/smart refresh reveals that
simple refresh windows with compositing on for the screen behave the same
as smart refresh windows. Smart refresh windows with compositing off use
more gfx memory than when compositing is on. Simple refresh windows with
compositing off will probably be more memory efficient, as we are using
an off-screen bitmap to render the browsing area anyway. However due to
this bitmap being re-used over multiple tabs/windows, it does not always
reflect what should be on the window, so performing a redraw of damaged
areas may be the only option. Need to read damaged regions from layer
(probably through struct Region *DamageList) and check on performance vs
memory or make the window refresh type configurable. Simple refresh code
#ifdefed out for now for further investigation later.
svn path=/trunk/netsurf/; revision=13464
Diffstat (limited to 'content')
0 files changed, 0 insertions, 0 deletions