color "0" was wrong
Origin commit data
------------------
Branch: ni/coolstream
Commit: 7096e701b6
Author: Thilo Graf <dbt@novatux.de>
Date: 2014-05-18 (Sun, 18 May 2014)
------------------
This commit was generated by Migit
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
------------------
Branch: ni/coolstream
Commit: b6c781f7e4
Author: Thilo Graf <dbt@novatux.de>
Date: 2014-05-11 (Sun, 11 May 2014)
------------------
This commit was generated by Migit
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
------------------
Branch: ni/coolstream
Commit: 6a2e701a7a
Author: Thilo Graf <dbt@novatux.de>
Date: 2014-05-05 (Mon, 05 May 2014)
------------------
This commit was generated by Migit
Origin commit data
------------------
Branch: ni/coolstream
Commit: d1b8246316
Author: Michael Liebmann <tuxcode.bbg@gmail.com>
Date: 2014-03-03 (Mon, 03 Mar 2014)
------------------
No further description and justification available within origin commit message!
------------------
This commit was generated by Migit
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
------------------
Branch: ni/coolstream
Commit: 23d7b62cf0
Author: Thilo Graf <dbt@novatux.de>
Date: 2014-03-03 (Mon, 03 Mar 2014)
------------------
This commit was generated by Migit
Percent value is related to current screen or parent size
Origin commit data
------------------
Branch: ni/coolstream
Commit: a33cad448a
Author: Thilo Graf <dbt@novatux.de>
Date: 2014-02-27 (Thu, 27 Feb 2014)
------------------
This commit was generated by Migit
Origin commit data
------------------
Branch: ni/coolstream
Commit: 9b18d0cf5b
Author: Thilo Graf <dbt@novatux.de>
Date: 2014-02-27 (Thu, 27 Feb 2014)
------------------
No further description and justification available within origin commit message!
------------------
This commit was generated by Migit
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
------------------
Branch: ni/coolstream
Commit: 8a897103ac
Author: Thilo Graf <dbt@novatux.de>
Date: 2014-02-27 (Thu, 27 Feb 2014)
------------------
This commit was generated by Migit
Origin commit data
------------------
Branch: ni/coolstream
Commit: 38dffb8456
Author: Thilo Graf <dbt@novatux.de>
Date: 2014-02-26 (Wed, 26 Feb 2014)
------------------
No further description and justification available within origin commit message!
------------------
This commit was generated by Migit
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
------------------
Branch: ni/coolstream
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 commit was generated by Migit
Origin commit data
------------------
Branch: ni/coolstream
Commit: f6d7352dca
Author: Thilo Graf <dbt@novatux.de>
Date: 2014-01-12 (Sun, 12 Jan 2014)
------------------
No further description and justification available within origin commit message!
------------------
This commit was generated by Migit
clear() replaces now clearCCItems() and cleanCCForm() is superfluous.
Origin commit data
------------------
Branch: ni/coolstream
Commit: ed7a2fd625
Author: Thilo Graf <dbt@novatux.de>
Date: 2014-01-07 (Tue, 07 Jan 2014)
------------------
This commit was generated by Migit
Origin commit data
------------------
Branch: ni/coolstream
Commit: 5f80ab6450
Author: [CST] Focus <focus.cst@gmail.com>
Date: 2013-11-27 (Wed, 27 Nov 2013)
------------------
No further description and justification available within origin commit message!
------------------
This commit was generated by Migit
Origin commit data
------------------
Branch: ni/coolstream
Commit: b8bd8c3704
Author: Thilo Graf <dbt@novatux.de>
Date: 2013-11-17 (Sun, 17 Nov 2013)
------------------
No further description and justification available within origin commit message!
------------------
This commit was generated by Migit
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
------------------
Branch: ni/coolstream
Commit: 8ae491a994
Author: Thilo Graf <dbt@novatux.de>
Date: 2013-11-08 (Fri, 08 Nov 2013)
------------------
This commit was generated by Migit
Was bad idea to rename. Other Classes can also inherit this. See CMenuTarget
Origin commit data
------------------
Branch: ni/coolstream
Commit: 6dd1da0628
Author: Thilo Graf <dbt@novatux.de>
Date: 2013-10-25 (Fri, 25 Oct 2013)
------------------
This commit was generated by Migit
There are too many name conflicts with hide-members in other classes.
Origin commit data
------------------
Branch: ni/coolstream
Commit: 6ee7fac1a5
Author: Thilo Graf <dbt@novatux.de>
Date: 2013-10-24 (Thu, 24 Oct 2013)
------------------
This commit was generated by Migit
Provides a unified header file, so it is not required to select a
certain header file.
Origin commit data
------------------
Branch: ni/coolstream
Commit: f7798affc6
Author: Thilo Graf <dbt@novatux.de>
Date: 2013-10-24 (Thu, 24 Oct 2013)
------------------
This commit was generated by Migit
