Radiotext moved into a separate class and will be shown with screensaver.
Origin commit data
------------------
Commit: d995d2b8f8
Author: Thilo Graf <dbt@novatux.de>
Date: 2020-01-05 (Sun, 05 Jan 2020)
Origin commit data
------------------
Commit: 3093f50831
Author: vanhofen <vanhofen@gmx.de>
Date: 2019-10-26 (Sat, 26 Oct 2019)
Origin message was:
------------------
- pick graphlcd support from DDT but include it in another way
Effect was right only for the osd_menu widget but not for all the
other opened menu widget instances. This was watched if user the osd setup menu
has lefted with the 'Setup' ('Menu') button. The main menu was not touched.
Thx GetAway for hint.
The use of slot in context with the OsdHelpers class should solve this
issue for all new generated menu widget instances.
Origin commit data
------------------
Commit: 538085ca6d
Author: Thilo Graf <dbt@novatux.de>
Date: 2019-04-07 (Sun, 07 Apr 2019)
use green button in favorites to show whats showing on primetime
Origin commit data
------------------
Commit: eb8b55fa72
Author: TangoCash <eric@loxat.de>
Date: 2019-03-03 (Sun, 03 Mar 2019)
For usage with other functions.
Origin commit data
------------------
Commit: 49667cc83e
Author: Thilo Graf <dbt@novatux.de>
Date: 2019-02-11 (Mon, 11 Feb 2019)
This option is not really specific for infobar.
Origin commit data
------------------
Commit: 82ae084343
Author: Thilo Graf <dbt@novatux.de>
Date: 2019-02-11 (Mon, 11 Feb 2019)
Don't working at the moment.
TODO: Make it usable for AX51/Mutant
Origin commit data
------------------
Commit: 7727d5f9f3
Author: Thilo Graf <dbt@novatux.de>
Date: 2018-04-29 (Sun, 29 Apr 2018)
This reverts commit 9401f2e8d1.
With this commit were crashes are to be expected. If here is an issue,
we should fix it with another solution.
Origin commit data
------------------
Commit: 9be66d824a
Author: Thilo Graf <dbt@novatux.de>
Date: 2018-04-11 (Wed, 11 Apr 2018)
This should avoid possible segfaults when user is calling color setup.
This behavior was observed if start wizard has been completed and
after that user wants to change color settings.
If target object is a singelton, this should not be an issue.
Origin commit data
------------------
Commit: 84612b795c
Author: Thilo Graf <dbt@novatux.de>
Date: 2018-04-11 (Wed, 11 Apr 2018)
Options were sometimes described ambiguously and previous behavior was no longer available.
Now the descriptions should be more plausible for current behavior.
Origin commit data
------------------
Commit: 89770bae19
Author: Thilo Graf <dbt@novatux.de>
Date: 2018-04-10 (Tue, 10 Apr 2018)
This reverts commit 1a68428f80 because of many
bothering compiler warnings:
extended initializer lists only available with -std=c++11 or -std=gnu++11
Origin commit data
------------------
Commit: adb80290ba
Author: vanhofen <vanhofen@gmx.de>
Date: 2018-04-04 (Wed, 04 Apr 2018)
getScreenWidth/HeightRel() was confusing because it depends on users window settings.
Replace names in old unused framebuffer code too.
Origin commit data
------------------
Commit: 86cdc12c8f
Author: vanhofen <vanhofen@gmx.de>
Date: 2018-01-22 (Mon, 22 Jan 2018)
Origin message was:
------------------
- framebuffer: better name for getWindowWidth/Height() functions
getScreenWidth/HeightRel() was confusing because it depends on users window settings.
Replace names in old unused framebuffer code too.
Origin commit data
------------------
Commit: e900d6610e
Author: vanhofen <vanhofen@gmx.de>
Date: 2018-01-22 (Mon, 22 Jan 2018)
Origin message was:
------------------
- osd-setup: start browsing for fonts in same dir were active font is located
remove double enum from CNeutrinoApp and move mostly used enum from NeutrinoMessages to new NeutrinoModes
Origin commit data
------------------
Commit: 028ec3cf3c
Author: vanhofen <vanhofen@gmx.de>
Date: 2017-11-20 (Mon, 20 Nov 2017)
Origin message was:
------------------
- neutrino: unify modes handling; ...
remove double enum from CNeutrinoApp and move mostly used enum from NeutrinoMessages to new NeutrinoModes
"using namespace std" in headers is considered bad practice, so move it
either into the respective cpp files or (for files which have lots of
other std::xxx usage anyway) just write it out explicitly.
Looking at the headers and the affected cpp files, one can actually see
why it is bad practice, as it's spreading very far ;-)
Origin commit data
------------------
Commit: 0d9139054a
Author: Stefan Seyfried <seife@tuxbox-git.slipkontur.de>
Date: 2017-10-01 (Sun, 01 Oct 2017)
