On Mon, 24 Feb 2020 at 7:06 pm, Giuseppe D'Angelo via Development < [email protected]> wrote:
> > > So, does anyone know the historical reasoning here, or any good reason > for not changing FocusScope just a normal property on Item? > > I don’t know the reason but if you just change it to a property you are going to find yourself debugging a lot of crashes and weird state from parent, children, and focus properties being evaluated before the focus scope property. If you were to defer all item focus evaluation to componentComplete() it might be workable though. If I really wanted to make it happen I think I’d try and work an attribute type of concept into the language. A property you can only assign a static value to and is guaranteed to be initialised before any bindings are evaluated. As or reasons for it to be its own type I’ve found the occasional need to walk the focus hierarchy myself and if the internal focus scope and sub focus item pointers were public that would have been a little less difficult. And logically the sub focus item property only belongs on FocusItems.
_______________________________________________ Development mailing list [email protected] https://lists.qt-project.org/listinfo/development
