...and color saturation added
- Use only the hue of base color for gradient
Origin commit data
------------------
Commit: 58224099fd
Author: Michael Liebmann <tuxcode.bbg@gmail.com>
Date: 2014-09-20 (Sat, 20 Sep 2014)
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)
This provides functinality for all sub classes too
Origin commit data
------------------
Commit: 581405e076
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)
Specifies that some certain operations especially eg. exec events for
that item are possible.
Origin commit data
------------------
Commit: 0c0e0e85ff
Author: Thilo Graf <dbt@novatux.de>
Date: 2014-09-02 (Tue, 02 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)
CComponentsForm provides page scroll if found more
than one pre defined page and is working with all derivated sub classes from CComponentsForm .
Pages are defined with setPageNumber(0...n) in items (1st page = 0). The item page number property is
defined in variable cc_page_number. The highest page number sets the
count of pages inside container to required value. Thats compellingly!
To show a page, we can use setCurrentPage(0...n ) and paintCurPage() or use directly paintPage(0...n).
Note: global paint() will show the current page. Default page is 0 (as first).
Use setCurrentPage(0...n) to change this before first call of paint().
Note: In CComponentsWindow class, these methods are applied to window body.
For examples, take a look into CTestMenu
Origin commit data
------------------
Commit: 672757606c
Author: Thilo Graf <dbt@novatux.de>
Date: 2014-06-26 (Thu, 26 Jun 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)
Value of is_painted is modified temporarily till next paint
of item
Not sure whether this is sufficiently or has bad side effects?
Origin commit data
------------------
Commit: b6c781f7e4
Author: Thilo Graf <dbt@novatux.de>
Date: 2014-05-11 (Sun, 11 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)
Percent value is related to current screen or parent size
Origin commit data
------------------
Commit: a33cad448a
Author: Thilo Graf <dbt@novatux.de>
Date: 2014-02-27 (Thu, 27 Feb 2014)
So it's possible to use this method for all cc-items.
setCenterPos() comes now with parameter 'along_mode' (CC_ALONG_X, CC_ALONG_Y).
So it's possible to center in x or y direction. As default are
both directions predefined.
Origin commit data
------------------
Commit: 8a897103ac
Author: Thilo Graf <dbt@novatux.de>
Date: 2014-02-27 (Thu, 27 Feb 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.
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)
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)
