When dealing with mouse events we use ChildAt() to find the controls
in the clicked area, but we may have hidden elements in the same position
in that case we want to dispatch events to the visible one. This patch
fixes this issue by filtering out the non visible elements.
Signed-off-by: Leandro Dorileo <leandro.maciel.dorileo@intel.com>
Whenever running through NextControl() also exclude those controls
which parents are also non visible.
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>
With this helper we may iterate over the control list and end up
not having any control that match the search criteria (namely: tabStop,
visible and enabled). In that case an index out of bounds error will
happen.
This patch checks for the resulting list and return if no control's
found.
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>
