also try to document the calling convention of this function
Origin commit data
------------------
Commit: 0c757d85c8
Author: Stefan Seyfried <seife@tuxbox-git.slipkontur.de>
Date: 2018-02-25 (Sun, 25 Feb 2018)
If filelist is empty or movie in filelist wasn't changed, just quit infoviewer
as in tv-mode. Otherwise start choosen movie.
Origin commit data
------------------
Commit: a1a028704b
Author: vanhofen <vanhofen@gmx.de>
Date: 2018-02-20 (Tue, 20 Feb 2018)
Origin message was:
------------------
- movieplayer: fix RC_ok handling while infoviewer is displayed; ...
If filelist is empty or movie in filelist wasn't changed, just quit infoviewer
as in tv-mode. Otherwise start choosen movie.
there was no update in movieplayer mode
Origin commit data
------------------
Commit: 10d9e1714c
Author: GetAway <get-away@t-online.de>
Date: 2018-02-20 (Tue, 20 Feb 2018)
Just for safety and to save resources.
Origin commit data
------------------
Commit: ab4762feed
Author: Thilo Graf <dbt@novatux.de>
Date: 2018-02-18 (Sun, 18 Feb 2018)
the implementation of the xp/yp handling in blit2FB is different on
different architectures, and the semantics are unclear, so just
calculate a buffer offset instead and use yp=0
Origin commit data
------------------
Commit: c8f6ff9a18
Author: Stefan Seyfried <seife@tuxbox-git.slipkontur.de>
Date: 2018-02-20 (Tue, 20 Feb 2018)
[vanhofen: was already ok in our code; just aligning code format]
Origin commit data
------------------
Commit: 25123fa63d
Author: Stefan Seyfried <seife@tuxbox-git.slipkontur.de>
Date: 2018-02-18 (Sun, 18 Feb 2018)
When the infobar timeout is disabled, the infobar was not shown for all
"automatic" events like "start" and "zap".
The purpose of disabled infobar timeout is to show the infobar all the
time (e.g. in radio mode), so this does not make sense. Fix it.
Origin commit data
------------------
Commit: 9cd7e8972c
Author: Stefan Seyfried <seife@tuxbox-git.slipkontur.de>
Date: 2018-02-04 (Sun, 04 Feb 2018)
next try to get rid of font artifacts:
* use kill() instead of hide() to force full repaint at next paint()
(this is probably not the best way, but works for now)
Origin commit data
------------------
Commit: 35890ee7c2
Author: Stefan Seyfried <seife@tuxbox-git.slipkontur.de>
Date: 2018-02-04 (Sun, 04 Feb 2018)
Origin message was:
------------------
infoviewer: force repaint of text fields
next try to get rid of font artifacts:
* use kill() instead of hide() to force full repaint at next paint()
(this is probably not the best way, but works for now)
hiding text boxes after resizing them will probably hide the new size
instead of the old one, so hide first, then resize
Origin commit data
------------------
Commit: 5ad063b590
Author: Stefan Seyfried <seife@tuxbox-git.slipkontur.de>
Date: 2018-02-04 (Sun, 04 Feb 2018)
With bigger font sizes, the the allocated space for satellite,
transponder and frequency was getting smaller.
Fix this by just keeping a safe space of 10 pixels to the radar icon.
Origin commit data
------------------
Commit: bbbc3267f3
Author: Stefan Seyfried <seife@tuxbox-git.slipkontur.de>
Date: 2018-02-04 (Sun, 04 Feb 2018)
some glyphs would still draw right of the allocated space,
fix the width calculation to avoid this
Origin commit data
------------------
Commit: 24b02050c0
Author: Stefan Seyfried <seife@tuxbox-git.slipkontur.de>
Date: 2018-02-04 (Sun, 04 Feb 2018)
at least with older freetype versions, font widths are not reported
reliably, so use a better way to determine the width and use a bigger
painting box for the fontrenderer so it does not skip rendering for
space reasons
Origin commit data
------------------
Commit: e3b76a11e4
Author: Stefan Seyfried <seife@tuxbox-git.slipkontur.de>
Date: 2018-01-28 (Sun, 28 Jan 2018)
instead of not even trying to draw glyphs that *might* extend past the
allocated space, actually draw as much as fits in the box
Origin commit data
------------------
Commit: 736964034c
Author: Stefan Seyfried <seife@tuxbox-git.slipkontur.de>
Date: 2018-01-28 (Sun, 28 Jan 2018)
