@tpaau17db Good documentation is hard :) - the reason here I would guess is that immediately constructing items is nearly always going to be a pessimisation. For example, if you create when "model" is set, but before geometry is known, you then have to lay out twice.
On the other hand, not knowing anything about your use-case, could you not have the binding you need in the delegate instead of doing it imperatively once children are constructed?


