If cc-item is bound on a parent form, it's not enough
to replace the item object only, also properties like
parent and index must be moved to new item to ensure that positions are calculated correctly.
But it's matter for unbound cc-items.
Origin commit data
------------------
Commit: c66c778326
Author: Thilo Graf <dbt@novatux.de>
Date: 2013-06-23 (Sun, 23 Jun 2013)
This also fixes a segfault in channellist when font settings
were changed und user is change back into channellist.
Origin commit data
------------------
Commit: 020d52ddbb
Author: Thilo Graf <dbt@novatux.de>
Date: 2013-06-18 (Tue, 18 Jun 2013)
Window comes now with footer and body
Origin commit data
------------------
Commit: 2a7c712f25
Author: Thilo Graf <dbt@novatux.de>
Date: 2013-06-16 (Sun, 16 Jun 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.
Is usable as default value for item position parameters
Origin commit data
------------------
Commit: 2a234d08ce
Author: Thilo Graf <dbt@novatux.de>
Date: 2013-06-12 (Wed, 12 Jun 2013)
- Default value is now 1 in CComponentsText
Origin commit data
------------------
Commit: ba1e514747
Author: Michael Liebmann <tuxcode.bbg@gmail.com>
Date: 2013-06-12 (Wed, 12 Jun 2013)
Origin commit data
------------------
Commit: 96da2f95b8
Author: FlatTV <FlatTV@gmx.de>
Date: 2013-06-06 (Thu, 06 Jun 2013)
Origin message was:
------------------
- CComponentsText: add possibility to set a text border
Assign real position values to progressbar if is bound (embedded) in a form.
This is dependently from its own parent status. Status of cc_parent==NULL
means, it's not bound and without parent form so we use x/y, otherwise
we use real values stored by cc_xr/cc_yr.
Values in cc_xr/cc_yr and cc_parent were assigned with addCCItem().
Signed-off-by: Michael Liebmann <tuxcode.bbg@gmail.com>
Origin commit data
------------------
Commit: fb812f38e8
Author: Thilo Graf <dbt@novatux.de>
Date: 2013-06-02 (Sun, 02 Jun 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)
Position of added items in subforms was fitted with wrong offset.
Usage of relative x/y position avoids wrong positions of items in subforms.
Origin commit data
------------------
Commit: d3d0bff7ac
Author: Thilo Graf <dbt@novatux.de>
Date: 2013-05-29 (Wed, 29 May 2013)
Origin commit data
------------------
Commit: 890d282315
Author: vanhofen <vanhofen@gmx.de>
Date: 2013-05-28 (Tue, 28 May 2013)
Origin message was:
------------------
- CComponentsHeader: add possibility to change font in header class
Some members are usable in subclasses, but current names could be not
suitable or not plausible with respect to the name of subclass.
Origin commit data
------------------
Commit: 8e46f63900
Author: Thilo Graf <dbt@novatux.de>
Date: 2013-05-27 (Mon, 27 May 2013)
Origin message was:
------------------
CComponentsHeader: rename some members for plausible usage in subclasses
Some members are usable in subclasses, but current names could be not
suitable or not plausible with respect to the name of subclass.
- 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
