diff options
author | Andreas Aardal Hanssen <andreas.aardal.hanssen@nokia.com> | 2009-09-11 12:10:12 (GMT) |
---|---|---|
committer | Andreas Aardal Hanssen <andreas.aardal.hanssen@nokia.com> | 2009-09-15 09:32:07 (GMT) |
commit | c8bf9bd17a4520eefe4306b7b1bb4f93fb296d80 (patch) | |
tree | 0126827048c3740a213d5be39b89074bd4d9ae01 /tests/auto/uic | |
parent | a06c7db92ff13a1f8a353851a586ae12755e7c6c (diff) | |
download | Qt-c8bf9bd17a4520eefe4306b7b1bb4f93fb296d80.zip Qt-c8bf9bd17a4520eefe4306b7b1bb4f93fb296d80.tar.gz Qt-c8bf9bd17a4520eefe4306b7b1bb4f93fb296d80.tar.bz2 |
Support for focus scopes: QGraphicsItem::ItemIsFocusScope.
This feature is essential for Declarative UI, but does not add much
value for C++ developers. A FocusScope provides a stack of focused
widgets, and it ensures that the topmost item on the stack has
focus if any of the items in the stack gains focus. When the topmost
loses focus, focus is passed to the "parent" focus scope, and so on.
You can get almost the same behavior using panels (ItemIsPanel),
except panels impose other behavior, like stopping clickfocus
propagation, and stopping event propagation in general. In a QML
world you would typically use FocusScope for controlling focus
locally, and panels when you need to maintain separate focus stacks.
Reviewed-by: akennedy
Diffstat (limited to 'tests/auto/uic')
0 files changed, 0 insertions, 0 deletions