We're using the wrong control to calculate the clipped area, it should
be the clipped control not its clipped parent.
Signed-off-by: Leandro Dorileo <leandro.maciel.dorileo@intel.com>
This patch introduce internal changes in order to #1 actually clip
content avoid growing parent's size and keeping controls with their
own pre-set sizes and also #2 add a scrollable feature to frame control.
Signed-off-by: Leandro Dorileo <leandro.maciel.dorileo@intel.com>
Currently when setting a control visible no matter if this control has
active children new KeyTab events will be dispatched. This results in
errors when an application has explicitly set the active control -
i.e with clui.ActivateControl().
In this case the expected behavior is to have that control active
instead of the next one, since we are not considering the the children
state then we always emit the KeyTab event resulting into a focus/active
status change.
This patch changes this behavior by querying the children's status and
checking if there is a child with active state set and only triggering
the KeyTab event when no child is active.
Signed-off-by: Leandro Dorileo <leandro.maciel.dorileo@intel.com>
This interface should be used to remove an object from its parental
chain, this destroyed object will not receive events nor will be
drawn neither will impact on other objects position and sizing.
These objects if properly handled could be eligible for collection
as well.
In order to guarantee BaseControl and Control are fully comparable in the
BaseControl level this patch introduces a refID interface, so the objects
can safely be comparable based on this interface.
