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)
The real position already used here, if item is bound to a parent.
(bound or embedded means: added with addCCItem() to a form)
This causes no separate calculation in paint methodes of embedded
sub items or sub forms and more nested sub forms.
CComponentsForm have also some new members
- exchangeCCItem() to exchange the order items
- setAppendOffset() to set an offset for auto append mode
Autoappend is enabled if x or y have value -1 (defined also in CC_APPEND)
x=horizontal, y=vertical
Is this activated, no separate calculation of incremental offset
is required.
However items with independent rendered parts, needs
a separate calculation. In some subclasses was this necessary.
Origin commit data
------------------
Commit: 04300f1874
Author: Thilo Graf <dbt@novatux.de>
Date: 2013-06-16 (Sun, 16 Jun 2013)
Origin message was:
------------------
CComponents: rework position handling
The real position already used here, if item is bound to a parent.
(bound or embedded means: added with addCCItem() to a form)
This causes no separate calculation in paint methodes of embedded
sub items or sub forms and more nested sub forms.
CComponentsForm have also some new members
- exchangeCCItem() to exchange the order items
- setAppendOffset() to set an offset for auto append mode
Autoappend is enabled if x or y have value -1 (defined also in CC_APPEND)
x=horizontal, y=vertical
Is this activated, no separate calculation of incremental offset
is required.
However items with independent rendered parts, needs
a separate calculation. In some subclasses was this necessary.
member value was not looped through
Origin commit data
------------------
Commit: f774eb833f
Author: Thilo Graf <dbt@novatux.de>
Date: 2013-04-25 (Thu, 25 Apr 2013)
Ensure empty pic object otherwise it can be retained on exit
of paintPicture(), if an instance of Infobox already exists.
supplement to ab59797ae5
Origin commit data
------------------
Commit: d7ce847471
Author: Thilo Graf <dbt@novatux.de>
Date: 2013-04-06 (Sat, 06 Apr 2013)
Origin commit data
------------------
Commit: 095c0e1b04
Author: Michael Liebmann <tuxcode.bbg@gmail.com>
Date: 2013-04-04 (Thu, 04 Apr 2013)
Origin message was:
------------------
* CComponentsInfoBox: CComponentsPicture not create when no image to draw
Background for text is not needed here
Origin commit data
------------------
Commit: 4e7f81a126
Author: Thilo Graf <dbt@novatux.de>
Date: 2013-04-04 (Thu, 04 Apr 2013)
Delete causes a clean background because it is possible that remnants are
left after changed font size.
Origin commit data
------------------
Commit: 9af63bdc72
Author: Thilo Graf <dbt@novatux.de>
Date: 2013-03-25 (Mon, 25 Mar 2013)
Ensures a clean environment for changed properties of a textbox in infobox.
Origin commit data
------------------
Commit: 0fa2bbc7c9
Author: Thilo Graf <dbt@novatux.de>
Date: 2013-03-18 (Mon, 18 Mar 2013)
It's easier to work with smaller files.
Most files contain only one cc-class and their names are
derived on the particular class that is contained therein.
Origin commit data
------------------
Commit: 3ed9af87ad
Author: Thilo Graf <dbt@novatux.de>
Date: 2013-02-26 (Tue, 26 Feb 2013)
