clear() removes only items and their instances inside button container, but all
other properties (e.g. width) are not touched. Re init should avoids this.
Origin commit data
------------------
Commit: 39fb9f47f4
Author: Thilo Graf <dbt@novatux.de>
Date: 2017-12-15 (Fri, 15 Dec 2017)
Is not really required.
Avoids possible compile/linker errors like "...no reference..." for some
coming changes.
Origin commit data
------------------
Commit: e9883cbd2d
Author: Thilo Graf <dbt@novatux.de>
Date: 2017-12-03 (Sun, 03 Dec 2017)
On hd51 and pc hardware was observed full visual timeout progress in message boxes.
Timeoout was displayed always without visible progress.
This should fix this.
Origin commit data
------------------
Commit: caface0a88
Author: Thilo Graf <dbt@novatux.de>
Date: 2017-11-23 (Thu, 23 Nov 2017)
remove double enum from CNeutrinoApp and move mostly used enum from NeutrinoMessages to new NeutrinoModes
Signed-off-by: Thilo Graf <dbt@novatux.de>
Origin commit data
------------------
Commit: 0fc3e793a4
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
Signed-off-by: Thilo Graf <dbt@novatux.de>
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
radius is allready calculatetd in base class src/gui/components/cc_frm.cpp
in member CComponentsForm::paintCCItems()
NOTE:
It seems the radius calculation inside framebuffer don't working correct
for corners on the right site on top and bottom.
Seen on hd51 hardware on osd-boxes with shadow
(e.g. infobar) or Boxes with frames e.g. on error message windows, buttons.
There are pixel errors like minimal holes on osd or displaced pixels.
On CST hardware evreything is ok.
Origin commit data
------------------
Commit: 94517d3404
Author: Thilo Graf <dbt@novatux.de>
Date: 2017-11-19 (Sun, 19 Nov 2017)
Origin message was:
------------------
src/gui/components/cc_frm_window.cpp: fix too small left bottom corner
radius is allready calculatetd in base class src/gui/components/cc_frm.cpp
in member CComponentsForm::paintCCItems()
NOTE:
It seems the radius calculation inside framebuffer don't working correct
for corners on the right site on top and bottom.
Seen on hd51 hardware on osd-boxes with shadow
(e.g. infobar) or Boxes with frames e.g. on error message windows, buttons.
There are pixel errors like minimal holes on osd or displaced pixels.
On CST hardware evreything is ok.
Origin commit data
------------------
Commit: 8aad36ed83
Author: vanhofen <vanhofen@gmx.de>
Date: 2017-10-14 (Sat, 14 Oct 2017)
Origin message was:
------------------
- cc-footer: remove our calcation of label-width; should now work automatically
Some parts were incomplete treated with defined parameter
'label_width' and/or 'chain_width'.
Origin commit data
------------------
Commit: c7a2dd70fc
Author: Thilo Graf <dbt@novatux.de>
Date: 2017-10-12 (Thu, 12 Oct 2017)
"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)
Otherwise shadows will be painted lower then the height of the object
the detailsline is docked to.
Origin commit data
------------------
Commit: 95ab4ac708
Author: vanhofen <vanhofen@gmx.de>
Date: 2017-09-25 (Mon, 25 Sep 2017)
Origin message was:
------------------
- detailsline: reduce two times the shadow width from the h_marks
Otherwise shadows will be painted lower then the height of the object
the detailsline is docked to.
Otherwise shadows will be painted lower then the height of the object
the detailsline is docked to.
Origin commit data
------------------
Commit: 0abccfac8a
Author: vanhofen <vanhofen@gmx.de>
Date: 2017-09-25 (Mon, 25 Sep 2017)
Origin message was:
------------------
- detailsline: reduce two times the shadow width from the h_marks
Otherwise shadows will be painted lower then the height of the object
the detailsline is docked to.
Decrement value removed.
Height of bottom marker was decreased on every new repaint if no new
height was assigned. Was to see in bouqueteditor while scrolling with bouqets or
channel select window.
comes in with e534457250
Origin commit data
------------------
Commit: dca7e10179
Author: Thilo Graf <dbt@novatux.de>
Date: 2017-09-24 (Sun, 24 Sep 2017)
Current count of chars could be not enough in some cases.
Origin commit data
------------------
Commit: ecdc1acb9f
Author: Thilo Graf <dbt@novatux.de>
Date: 2017-09-20 (Wed, 20 Sep 2017)
