- outsourced some classes cc_item.cpp/h, cc_draw.cpp/h
- added extra methodes for simple use of some basic components extra.cpp/h
- rework clock handling: use timer class, reworked members for
enable/disable clock with external timer events,
tryed to fix some display issues related with infoclock and
time osd clock in moviebrowser, channellist, menuus
- reworked hide/kill handling, removed parameter for hide(), try to use
cached backgrounds for other constallations, paint cache, image cache (all beta)
- reworked shadow/frame handling, add shadow modes for left/right
arrangement, TODO: repaint for existant instances required
- reworked color gradient assignment (beta)
... Note: I had a data crash in my local git tree
and i tryed to restore my historie, but most was lost. Therefore here
the commit is large
Origin commit data
------------------
Commit: 0146511f38
Author: Thilo Graf <dbt@novatux.de>
Date: 2015-11-18 (Wed, 18 Nov 2015)
Origin message was:
------------------
components: rework classes
- outsourced some classes cc_item.cpp/h, cc_draw.cpp/h
- added extra methodes for simple use of some basic components extra.cpp/h
- rework clock handling: use timer class, reworked members for
enable/disable clock with external timer events,
tryed to fix some display issues related with infoclock and
time osd clock in moviebrowser, channellist, menuus
- reworked hide/kill handling, removed parameter for hide(), try to use
cached backgrounds for other constallations, paint cache, image cache (all beta)
- reworked shadow/frame handling, add shadow modes for left/right
arrangement, TODO: repaint for existant instances required
- reworked color gradient assignment (beta)
... Note: I had a data crash in my local git tree
and i tryed to restore my historie, but most was lost. Therefore here
the commit is large
Color gradient feature was originally intended for use
inside theme settings and it's not really suitable for
generally use as default in all themes at the moment, so it makes more
sense to have options in theme settings and let the user decide
to customize this, unless enough other gui parts can use this feature.
Origin commit data
------------------
Commit: 01516cf943
Author: Thilo Graf <dbt@novatux.de>
Date: 2015-04-29 (Wed, 29 Apr 2015)
Origin message was:
------------------
themes: use hintbox and header gradient option in theme settings
Color gradient feature was originally intended for use
inside theme settings and it's not really suitable for
generally use as default in all themes at the moment, so it makes more
sense to have options in theme settings and let the user decide
to customize this, unless enough other gui parts can use this feature.
This provides possibility to set relevant gradiant properties in cc sub classes
Origin commit data
------------------
Commit: f9147d185a
Author: Thilo Graf <dbt@novatux.de>
Date: 2014-09-20 (Sat, 20 Sep 2014)
Use convention for cc classes.
paintGradient probaly too general and
is related to body, other fb types can be also handled with gradient.
Origin commit data
------------------
Commit: 83070da483
Author: Thilo Graf <dbt@novatux.de>
Date: 2014-09-20 (Sat, 20 Sep 2014)
Variable now usable via g_settings in all subclasses. enable/disable.
TODO: gradient type handling
Origin commit data
------------------
Commit: 64c84fb490
Author: Thilo Graf <dbt@novatux.de>
Date: 2014-09-20 (Sat, 20 Sep 2014)
This can help to handle some useful values for any functions
Origin commit data
------------------
Commit: 67a42c3e96
Author: Thilo Graf <dbt@novatux.de>
Date: 2014-08-25 (Mon, 25 Aug 2014)
Allows a simplified implementation without prior declaration and
initialisation
Origin commit data
------------------
Commit: 53cf57876c
Author: Thilo Graf <dbt@novatux.de>
Date: 2014-05-30 (Fri, 30 May 2014)
paintBackgroundBoxRel() ignores rounded corners. This avoids painting of
undesirable parts on corners.
Origin commit data
------------------
Commit: dc007e810a
Author: Thilo Graf <dbt@novatux.de>
Date: 2014-05-18 (Sun, 18 May 2014)
kill() allows now paint with defined colors over rendered objects
without restore of background. It's similar to paintBackgroundBoxRel()
known from CFrameBuffer, but with possiblity to define color,
default color is 0 like before (empty background).
Items with parent bindings use the background color of its parent
as default, but can also be ignored.
This function can be useful before repaint of items and/or,
if required, to have a clean background inside item containers.
Origin commit data
------------------
Commit: 6a2e701a7a
Author: Thilo Graf <dbt@novatux.de>
Date: 2014-05-05 (Mon, 05 May 2014)
Use strictly CComponentsForm as parent parameter in constructors.
Some parts have been cleaned up (Constructors, init methodes removed)
New parameter makes it possible already add current item in constructor.
So in mostly situations is it not necessary to use explicit addCCItem(),
but addCCItem()is still valid and necessary in certain situations.
Affected are all cc-classes and their derivates.
Some classes must or can be adapted later. The function is
not currently restricted, because usage of parent parameter is not explicit
defined in constructors, see CImageInfo, here yet are used addCCItem()
methodes.
Generally this parameter is located in the constructors before bool has_shadow,
but it is not sure whether it would be better to use this parameter as the first.
That remains to be clarified.
Origin commit data
------------------
Commit: 23d7b62cf0
Author: Thilo Graf <dbt@novatux.de>
Date: 2014-03-03 (Mon, 03 Mar 2014)
This check happens several times, therefore it is senseful, to move into own member.
Function returns false on error and is used here to show an error message if
something was wrong.
Such errors can happen on position or dimension errors e.g. out of screen or
too large display values.
Note: this is only an emergency helper for debugging on
fatal errors during developing of window stuff. Mostly errors
of this kind causing crashes and must be fixed.
Origin commit data
------------------
Commit: f813b9ea98
Author: Thilo Graf <dbt@novatux.de>
Date: 2014-02-23 (Sun, 23 Feb 2014)
Origin message was:
------------------
CComponents: add member CheckFbData() for fbdata check
This check happens several times, therefore it is senseful, to move into own member.
Function returns false on error and is used here to show an error message if
something was wrong.
Such errors can happen on position or dimension errors e.g. out of screen or
too large display values.
Note: this is only an emergency helper for debugging on
fatal errors during developing of window stuff. Mostly errors
of this kind causing crashes and must be fixed.
This causes an unnecessary offset and possible fb-remains.
This was observed at the header in Imageinfo, but only without shadow.
Origin commit data
------------------
Commit: 57a6c36329
Author: Thilo Graf <dbt@novatux.de>
Date: 2014-01-31 (Fri, 31 Jan 2014)
This shows also x or y values < 0.
Origin commit data
------------------
Commit: 39d6340598
Author: Thilo Graf <dbt@novatux.de>
Date: 2014-01-18 (Sat, 18 Jan 2014)
clear() replaces now clearCCItems() and cleanCCForm() is superfluous.
Origin commit data
------------------
Commit: ed7a2fd625
Author: Thilo Graf <dbt@novatux.de>
Date: 2014-01-07 (Tue, 07 Jan 2014)
- if dx, dy == 0, it is not senseful to save screen.
- delete[] v_fbdata[i].pixbuf is also called in clear()
Origin commit data
------------------
Commit: 9b299824d6
Author: Thilo Graf <dbt@novatux.de>
Date: 2013-12-22 (Sun, 22 Dec 2013)
__func__ is more suitable for portability
Origin commit data
------------------
Commit: 8442b39c28
Author: Thilo Graf <dbt@novatux.de>
Date: 2013-12-15 (Sun, 15 Dec 2013)
Value 0 for embedded items should be unproblematic, buy single items
should have minimum value = 1.
Origin commit data
------------------
Commit: e5b0673259
Author: Thilo Graf <dbt@novatux.de>
Date: 2013-11-10 (Sun, 10 Nov 2013)
This causes initialization of all properties, but
affects the behavior of item paint.
This can be understood as a counterpart to isPainted().
Origin commit data
------------------
Commit: 8ae491a994
Author: Thilo Graf <dbt@novatux.de>
Date: 2013-11-08 (Fri, 08 Nov 2013)
Was bad idea to rename. Other Classes can also inherit this. See CMenuTarget
Origin commit data
------------------
Commit: 6dd1da0628
Author: Thilo Graf <dbt@novatux.de>
Date: 2013-10-25 (Fri, 25 Oct 2013)
There are too many name conflicts with hide-members in other classes.
Origin commit data
------------------
Commit: 6ee7fac1a5
Author: Thilo Graf <dbt@novatux.de>
Date: 2013-10-24 (Thu, 24 Oct 2013)
Provides a unified header file, so it is not required to select a
certain header file.
Origin commit data
------------------
Commit: f7798affc6
Author: Thilo Graf <dbt@novatux.de>
Date: 2013-10-24 (Thu, 24 Oct 2013)
These attributes are better placed in the basic class.
Origin commit data
------------------
Commit: 3c5f4867fb
Author: Thilo Graf <dbt@novatux.de>
Date: 2013-05-31 (Fri, 31 May 2013)
- Paint rounded corners only where it is required
- Skip paint frame/paint shadow, if not defined
Origin commit data
------------------
Commit: 4da83b546c
Author: Michael Liebmann <tuxcode.bbg@gmail.com>
Date: 2013-05-24 (Fri, 24 May 2013)
Origin message was:
------------------
* CComponents: Reworked paint the shadows
- Paint rounded corners only where it is required
- Skip paint frame/paint shadow, if not defined
- Use CFrameBuffer::waitForIdle() to ensure that all GXA commands
are finished before SaveScreen() / RestoreScreen() is executed
Origin commit data
------------------
Commit: 072097cd06
Author: Michael Liebmann <tuxcode.bbg@gmail.com>
Date: 2013-05-17 (Fri, 17 May 2013)
Origin message was:
------------------
* Fix CComponents::getScreen()/hide() & CComponentsItem::hideCCItem()
- Use CFrameBuffer::waitForIdle() to ensure that all GXA commands
are finished before SaveScreen() / RestoreScreen() is executed
Exit in initVarItem() on !paint_bg was too early.
Origin commit data
------------------
Commit: 9ae72bf02d
Author: Thilo Graf <dbt@novatux.de>
Date: 2013-05-12 (Sun, 12 May 2013)
Origin commit data
------------------
Commit: 309b371060
Author: Michael Liebmann <tuxcode.bbg@gmail.com>
Date: 2013-05-08 (Wed, 08 May 2013)
Origin message was:
------------------
* CComponents::paintFbItems: Don't paint item if dx or dy are 0
There was some problems with restore, hide, clean and save background of item parts,
seen in detailsline. kill() worked not really clean.
kill() works now as virtual member and uses paintBackgroundBoxRel().
In consequence of which:
-unnecessary members in subclasses removed.
-add some comments
Origin commit data
------------------
Commit: a4c3e08f77
Author: Thilo Graf <dbt@novatux.de>
Date: 2013-05-03 (Fri, 03 May 2013)
not used in sub classes
Origin commit data
------------------
Commit: d7c35b07e4
Author: Thilo Graf <dbt@novatux.de>
Date: 2013-04-14 (Sun, 14 Apr 2013)
