return value = current id of added item
Origin commit data
------------------
Commit: 888c575ef4
Author: Thilo Graf <dbt@novatux.de>
Date: 2015-12-01 (Tue, 01 Dec 2015)
- outsourced some classes cc_item.cpp/h, cc_draw.cpp/h
- added extra methodes for simple use of some basic components extra.cpp/h
- rework clock handling: use timer class, reworked members for
enable/disable clock with external timer events,
tryed to fix some display issues related with infoclock and
time osd clock in moviebrowser, channellist, menuus
- reworked hide/kill handling, removed parameter for hide(), try to use
cached backgrounds for other constallations, paint cache, image cache (all beta)
- reworked shadow/frame handling, add shadow modes for left/right
arrangement, TODO: repaint for existant instances required
- reworked color gradient assignment (beta)
... Note: I had a data crash in my local git tree
and i tryed to restore my historie, but most was lost. Therefore here
the commit is large
Origin commit data
------------------
Commit: 0146511f38
Author: Thilo Graf <dbt@novatux.de>
Date: 2015-11-18 (Wed, 18 Nov 2015)
Origin message was:
------------------
components: rework classes
- outsourced some classes cc_item.cpp/h, cc_draw.cpp/h
- added extra methodes for simple use of some basic components extra.cpp/h
- rework clock handling: use timer class, reworked members for
enable/disable clock with external timer events,
tryed to fix some display issues related with infoclock and
time osd clock in moviebrowser, channellist, menuus
- reworked hide/kill handling, removed parameter for hide(), try to use
cached backgrounds for other constallations, paint cache, image cache (all beta)
- reworked shadow/frame handling, add shadow modes for left/right
arrangement, TODO: repaint for existant instances required
- reworked color gradient assignment (beta)
... Note: I had a data crash in my local git tree
and i tryed to restore my historie, but most was lost. Therefore here
the commit is large
This avoids unnecessary flicker effects, because no paint is required,
if page count = 1 and also ensures, that this page is defined as current page.
Origin commit data
------------------
Commit: 23c708b787
Author: Thilo Graf <dbt@novatux.de>
Date: 2014-10-05 (Sun, 05 Oct 2014)
If we have a frame around parent item, ensure matching corners
inside of embedded item, this avoids ugly unpainted spaces
between frame and item border.
TODO: other constellations are not considered at the moment!
Origin commit data
------------------
Commit: 09851f3b9f
Author: Thilo Graf <dbt@novatux.de>
Date: 2014-10-04 (Sat, 04 Oct 2014)
frame width was not considered
Origin commit data
------------------
Commit: f7faf07ab1
Author: Thilo Graf <dbt@novatux.de>
Date: 2014-10-04 (Sat, 04 Oct 2014)
This provides page scroll with up/down, left/right or combined.
Usage of exec() methods with implemented signals allows a
generic implematation of button or other message handling with
signal/slot solutions.
still to do: page cache
Origin commit data
------------------
Commit: 88ce62ea84
Author: Thilo Graf <dbt@novatux.de>
Date: 2014-09-07 (Sun, 07 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)
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)
This should be done in the arrangement of the container contents
Origin commit data
------------------
Commit: dce25e94b3
Author: Thilo Graf <dbt@novatux.de>
Date: 2014-06-22 (Sun, 22 Jun 2014)
This methode is an equivalent version of CComponentsItem::kill() and
allows to erase all items inside of a container at once.
Origin commit data
------------------
Commit: 581b9c7701
Author: Thilo Graf <dbt@novatux.de>
Date: 2014-06-05 (Thu, 05 Jun 2014)
CComponentsHeader uses now CComponentsIconForm, which is now derived
from CComponentsFrmChain. Some methods should be now simplified and
allow to handle some modifications easier.
Origin commit data
------------------
Commit: 6fe7b452c1
Author: Thilo Graf <dbt@novatux.de>
Date: 2014-03-22 (Sat, 22 Mar 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)
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)
Some calculations can resulting odd values and can provocate
unnecessary debug spam, but more lines should be repaired.
Origin commit data
------------------
Commit: a0a4cc1355
Author: Thilo Graf <dbt@novatux.de>
Date: 2014-01-06 (Mon, 06 Jan 2014)
Function parameter 'cc_Items' should be passed by reference (performance).
Origin commit data
------------------
Commit: abe1de16b0
Author: Thilo Graf <dbt@novatux.de>
Date: 2013-12-24 (Tue, 24 Dec 2013)
CComponentsFrmChain provides a form for chained cc-items with
optional dynamic arrangement or direction parameters
Origin commit data
------------------
Commit: eb16ea3ac6
Author: Thilo Graf <dbt@novatux.de>
Date: 2013-12-23 (Mon, 23 Dec 2013)
__func__ is more suitable for portability
Origin commit data
------------------
Commit: 8442b39c28
Author: Thilo Graf <dbt@novatux.de>
Date: 2013-12-15 (Sun, 15 Dec 2013)
0 could make problems on fit items into container
Origin commit data
------------------
Commit: ad80daea96
Author: Thilo Graf <dbt@novatux.de>
Date: 2013-12-04 (Wed, 04 Dec 2013)
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)
This saves explicit position calculations to arrange items centered
Origin commit data
------------------
Commit: 3ff09c88bd
Author: Thilo Graf <dbt@novatux.de>
Date: 2013-10-11 (Fri, 11 Oct 2013)
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
------------------
Commit: 4eb26988e9
Author: Thilo Graf <dbt@novatux.de>
Date: 2013-09-08 (Sun, 08 Sep 2013)
Frame of form was overpainted by item,
small whitespace fixes
Origin commit data
------------------
Commit: 5cb7d66993
Author: Thilo Graf <dbt@novatux.de>
Date: 2013-08-28 (Wed, 28 Aug 2013)
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
------------------
Commit: 75fe48043e
Author: Thilo Graf <dbt@novatux.de>
Date: 2013-06-23 (Sun, 23 Jun 2013)
push_back doesn't make all necessary steps to add an item
Origin commit data
------------------
Commit: 460c8bbff3
Author: Thilo Graf <dbt@novatux.de>
Date: 2013-06-23 (Sun, 23 Jun 2013)
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)
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.
