we're going to use the STFB blitter instead of manually
scaling everything if the videomode is not 720p, so more
or less revert all commits regarding FB scaling:
Revert "fontrenderer: scale fonts for nonstandard FB resolutions"
Revert "neutrino: resize framebuffer on videomode change"
Revert "fontrenderer: fix issue with epgwindow font when FB is scaling"
Revert "neutrino: fix artefacts with scaling framebuffer and 1080i"
Revert "spark: draw lines 2px wide instead of 1 in full-HD mode"
Revert "spark: do not scale framebuffer for PAL mode"
Revert "spark: fix framebuffer glitches"
Revert "spark: do not sync blitter after every rectangle (improves performance)"
Origin commit data
------------------
Commit: 7fcd36ed66
Author: Stefan Seyfried <seife@tuxbox-git.slipkontur.de>
Date: 2012-03-31 (Sat, 31 Mar 2012)
this is needed on spark because the framebuffer has the same resolution
as the video plane...
Origin commit data
------------------
Commit: b34e7205b9
Author: Stefan Seyfried <seife@tuxbox-git.slipkontur.de>
Date: 2012-02-22 (Wed, 22 Feb 2012)
both functions had slightly different ideas on how wide a string
would render, leading to occational off-by-ones and eventually
stripped characters
git-svn-id: file:///home/bas/coolstream_public_svn/THIRDPARTY/applications/neutrino-experimental@1264 e54a6e83-5905-42d5-8d5c-058d10e6a962
Origin commit data
------------------
Commit: f0d56fe6e7
Author: Stefan Seyfried <seife@tuxbox-git.slipkontur.de>
Date: 2011-03-06 (Sun, 06 Mar 2011)
'\n' in a text was not working correctly - it did not reset the
X position correctly and it did jump out of the assigned box.
Visible errors were e.g. on epgplus, 13.0E SF1, where the short
description often contains '\n' and thus garbage was painted
below the epgplus window (and did not get cleared afterwards).
For now we replace '\n' with '¶' (0x00b6). Later, if no offenders
are found, it should simply be removed.
git-svn-id: file:///home/bas/coolstream_public_svn/THIRDPARTY/applications/neutrino-experimental@872 e54a6e83-5905-42d5-8d5c-058d10e6a962
Origin commit data
------------------
Commit: b666fab10b
Author: Stefan Seyfried <seife@tuxbox-git.slipkontur.de>
Date: 2010-10-31 (Sun, 31 Oct 2010)
do not paint the background color, making the font "transparent"
this works around display problems in e.g. streaminfo, because the
"wrong" background color is used
git-svn-id: file:///home/bas/coolstream_public_svn/THIRDPARTY/applications/neutrino-experimental@224 e54a6e83-5905-42d5-8d5c-058d10e6a962
Origin commit data
------------------
Commit: 6b4f0ad178
Author: Stefan Seyfried <seife@tuxbox-git.slipkontur.de>
Date: 2010-01-30 (Sat, 30 Jan 2010)
Speed up the fontrenderer by *not* using the GXA accelerator. To
prevent artifacts, add a routine to framebuffer class to sync on
the GXA engine being ready with drawing.
git-svn-id: file:///home/bas/coolstream_public_svn/THIRDPARTY/applications/neutrino-experimental@196 e54a6e83-5905-42d5-8d5c-058d10e6a962
Origin commit data
------------------
Commit: 230a966e7d
Author: Stefan Seyfried <seife@tuxbox-git.slipkontur.de>
Date: 2010-01-20 (Wed, 20 Jan 2010)
* freetype errors are != 0, not < 0, fix that to avoid segfaults in
case of invalid fonts
* unlock the render mutex in case of an error
git-svn-id: file:///home/bas/coolstream_public_svn/THIRDPARTY/applications/neutrino-experimental@42 e54a6e83-5905-42d5-8d5c-058d10e6a962
Origin commit data
------------------
Commit: 5345573e5e
Author: Stefan Seyfried <seife@tuxbox-git.slipkontur.de>
Date: 2009-12-13 (Sun, 13 Dec 2009)
Origin message was:
------------------
fontrenderer: improve freetype error handling
* freetype errors are != 0, not < 0, fix that to avoid segfaults in
case of invalid fonts
* unlock the render mutex in case of an error
git-svn-id: file:///home/bas/coolstream_public_svn/THIRDPARTY/applications/neutrino-experimental@42 e54a6e83-5905-42d5-8d5c-058d10e6a962
