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.
The combination of infobox handling and screen size management doesn't
really fit together. Particular it could be better implemented some
inheritance, because incorporated functions and variables are
redundant and so the classes can be better coordinated.
Moreover, it doesn't seem sensible to use only a part of the display.
The use of full screen instead of window could simplify a lot.
Current state of CChannelList is mostly not compatible with CC-classes and
implementations are to expensive at the moment, because more preparations are necessary.
- add var for object index
can be usefull for identifications of objects for focus operations soon
- add default value for screen size (30%) to CComponentsPIP constructor
most size we mostly use is 30% of size
- add setters for screen_w and screen_h
also this can be usefull t adapt screen sizes e.g. during
runtime operations
Small helper for detection of item types.
This could be useful, if it is necessary, to track these at runtime or
debugging, because it's not really detectable, which items just be used.
e.g forms could contain very much items, but many of these items
are inherited from CComponentsItem and an assignment to a certain subclass.
Inherited methodes like insertCCItem, removeCCItem ... don't work
nice, if cc-items are ititialized too late. If we init in constructors,
we can manipulate header items, otherwise not.
clearCCItems() is to find in the destructor, and should be called with
delete.
Handle with care!
If is x or y position of embedded item out of allowed form dimension, then
set a new x or y value to item.
Added debug message should help to find issues.
Use addHeaderButton() to add any button icon ont header form.
The buttons have a right alignment, this means, the first button
is on the right boarder of header.
For existing instances it's recommended to remove old button icons
before add new buttons, otherwise icons will be append.
See also sample code in CTestMenu.
Collects only icons.You can add icons step by step or
with a vector and paint the form at once.
Width and height are dynamic calculated if parameters
width or height are smaller then summary of lenght of all added icons.
It's also possible to manipulate the icon array with members:
- insertIcon()
- removeIcon()
- removeAllIcons()
TODO: support for resizable images
