Jonathan,
appreciate your elaborate answer. I arrived at the same conlusion, not
to use the "official" FocusModel. There wasn't any hope to get changes
for 2.2 anyway. It just felt as if it could have been a good match
because a subset of it would fit perfectly, namely the focused item
property and methods to focus the next/prev item. I wouldn't have
supported a pluggable focusmodel anyway, there's not much to gain from that.
In the end I guess my point is that TreeView and TreeTableView would
have benefitted from the above mentioned subset with item-based focusing
as well. In a treeview you don't really care about the focused index. I
think. Especially if it changes everytime something is expanded or
collapsed. And ListView etc. would extend that simple focusmodel to add
index-based focus operations.
As to the "fake" focus inside a listview vs this property sheet
component: currently I am supporting something like a focused row with
property name and editor. This row is highlighted and can be
(fake-)focused even if the property editor is disabled. So it is similar
to a Listview. Basically, having a fake focus does not mean I cannot
have a "real" focus on a property editor, too ;-)
Werner
