This saves explicit position calculations to arrange items centered
Origin commit data
------------------
Branch: ni/coolstream
Commit: 3ff09c88bd
Author: Thilo Graf <dbt@novatux.de>
Date: 2013-10-11 (Fri, 11 Oct 2013)
------------------
This commit was generated by Migit
CComponentsForm: Overload member removeCCItem so we can use
cc_item as parameter.
CComponentsWindow: add member bool showFooter().
This allows to hide a footer in window.
Origin commit data
------------------
Branch: ni/coolstream
Commit: 4eb26988e9
Author: Thilo Graf <dbt@novatux.de>
Date: 2013-09-08 (Sun, 08 Sep 2013)
------------------
This commit was generated by Migit
Frame of form was overpainted by item,
small whitespace fixes
Origin commit data
------------------
Branch: ni/coolstream
Commit: 5cb7d66993
Author: Thilo Graf <dbt@novatux.de>
Date: 2013-08-28 (Wed, 28 Aug 2013)
------------------
This commit was generated by Migit
Origin commit data
------------------
Branch: ni/coolstream
Commit: f3cb2bc41c
Author: Thilo Graf <dbt@novatux.de>
Date: 2013-06-25 (Tue, 25 Jun 2013)
------------------
No further description and justification available within origin commit message!
------------------
This commit was generated by Migit
Origin commit data
------------------
Branch: ni/coolstream
Commit: 7fd870a063
Author: Thilo Graf <dbt@novatux.de>
Date: 2013-06-25 (Tue, 25 Jun 2013)
------------------
No further description and justification available within origin commit message!
------------------
This commit was generated by Migit
It's not enough to insert an item object only. Also properties like
parent and index must be defined to inserted item to ensure that
positions are calculated correctly.
Origin commit data
------------------
Branch: ni/coolstream
Commit: 75fe48043e
Author: Thilo Graf <dbt@novatux.de>
Date: 2013-06-23 (Sun, 23 Jun 2013)
------------------
This commit was generated by Migit
push_back doesn't make all necessary steps to add an item
Origin commit data
------------------
Branch: ni/coolstream
Commit: 460c8bbff3
Author: Thilo Graf <dbt@novatux.de>
Date: 2013-06-23 (Sun, 23 Jun 2013)
------------------
This commit was generated by Migit
Origin commit data
------------------
Branch: ni/coolstream
Commit: a8721fa72a
Author: Thilo Graf <dbt@novatux.de>
Date: 2013-06-23 (Sun, 23 Jun 2013)
------------------
No further description and justification available within origin commit message!
------------------
This commit was generated by Migit
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
------------------
Branch: ni/coolstream
Commit: c66c778326
Author: Thilo Graf <dbt@novatux.de>
Date: 2013-06-23 (Sun, 23 Jun 2013)
------------------
This commit was generated by Migit
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
------------------
Branch: ni/coolstream
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.
------------------
This commit was generated by Migit
Origin commit data
------------------
Branch: ni/coolstream
Commit: f968abe6c5
Author: Thilo Graf <dbt@novatux.de>
Date: 2013-06-12 (Wed, 12 Jun 2013)
------------------
No further description and justification available within origin commit message!
------------------
This commit was generated by Migit
Origin commit data
------------------
Branch: ni/coolstream
Commit: 2af1c5d8b2
Author: Thilo Graf <dbt@novatux.de>
Date: 2013-06-12 (Wed, 12 Jun 2013)
------------------
No further description and justification available within origin commit message!
------------------
This commit was generated by Migit
Origin commit data
------------------
Branch: ni/coolstream
Commit: d862de87eb
Author: Thilo Graf <dbt@novatux.de>
Date: 2013-06-08 (Sat, 08 Jun 2013)
------------------
No further description and justification available within origin commit message!
------------------
This commit was generated by Migit
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
------------------
Branch: ni/coolstream
Commit: d3d0bff7ac
Author: Thilo Graf <dbt@novatux.de>
Date: 2013-05-29 (Wed, 29 May 2013)
------------------
This commit was generated by Migit
Helpers to identfie added items.
Origin commit data
------------------
Branch: ni/coolstream
Commit: ddaa7a876e
Author: Thilo Graf <dbt@novatux.de>
Date: 2013-05-29 (Wed, 29 May 2013)
------------------
This commit was generated by Migit
Pointer is typically of type CComponentsForm or derived classes,
default intialized with NULL and serves to access for
properties of parent object by embedded items.
Origin commit data
------------------
Branch: ni/coolstream
Commit: 336c3bc7a1
Author: Thilo Graf <dbt@novatux.de>
Date: 2013-04-15 (Mon, 15 Apr 2013)
------------------
This commit was generated by Migit
Origin commit data
------------------
Branch: ni/coolstream
Commit: 39a4e3400e
Author: Thilo Graf <dbt@novatux.de>
Date: 2013-04-15 (Mon, 15 Apr 2013)
------------------
No further description and justification available within origin commit message!
------------------
This commit was generated by Migit
If items are used in forms it can be usefully to have a variable
which contains the real position on screen.
This can happen e.g. if an item contains separate render methods, because within forms
usual x/y values related to form dimensions and be converted.
Origin commit data
------------------
Branch: ni/coolstream
Commit: 62efe2cb59
Author: Thilo Graf <dbt@novatux.de>
Date: 2013-04-10 (Wed, 10 Apr 2013)
------------------
This commit was generated by Migit
Origin commit data
------------------
Branch: ni/coolstream
Commit: 8d8ce4c55a
Author: Stefan Seyfried <seife@tuxbox-git.slipkontur.de>
Date: 2013-04-06 (Sat, 06 Apr 2013)
------------------
No further description and justification available within origin commit message!
------------------
This commit was generated by Migit
Origin commit data
------------------
Branch: ni/coolstream
Commit: d391bedd5f
Author: Thilo Graf <dbt@novatux.de>
Date: 2013-03-26 (Tue, 26 Mar 2013)
------------------
No further description and justification available within origin commit message!
------------------
This commit was generated by Migit
Origin commit data
------------------
Branch: ni/coolstream
Commit: 0dc4686874
Author: Thilo Graf <dbt@novatux.de>
Date: 2013-03-20 (Wed, 20 Mar 2013)
------------------
No further description and justification available within origin commit message!
------------------
This commit was generated by Migit
Handling of minitv items are different to other item types
and need an explizit call of hide(). So it is possible to hide a form-
object without a extra call of hide() for minitv objects.
Origin commit data
------------------
Branch: ni/coolstream
Commit: 69476903ee
Author: Thilo Graf <dbt@novatux.de>
Date: 2013-03-14 (Thu, 14 Mar 2013)
------------------
This commit was generated by Migit
Some items had multiple inits and some calls of clearCCItems()
have caused segfaults, hope this fix this.
Origin commit data
------------------
Branch: ni/coolstream
Commit: 4a931af6ef
Author: Thilo Graf <dbt@novatux.de>
Date: 2013-03-13 (Wed, 13 Mar 2013)
------------------
This commit was generated by Migit
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
------------------
Branch: ni/coolstream
Commit: 3ed9af87ad
Author: Thilo Graf <dbt@novatux.de>
Date: 2013-02-26 (Tue, 26 Feb 2013)
------------------
This commit was generated by Migit
