While trying to recreate an editor window I made back when UI toolkit wasnt a thing yet, I was met with a problem really hard to overcome. With ReorderableList it was very easy to populate the view with different looking entries, as while creating/drawing an element it was possible to access index of an item being drawn. Now trying to do the same with a ListView it seems impossible to add different visual element depending on what index is being drawn, the only information we get about it is while binding, which makes it possible to alter some internal state of visual element, changing the way it is drawn, but still, it would be much easier to be able to add different visual element, and not the same with alterable state.
Items of the list view are reused and are not tied to a specific index. We essentially create a pool of them. Then they get bound to the indices they will display only later. If something is index specific, it is necessary to be in the bind/unbind.
You can put all the logic inside the bind if needed, and let the makeItem return an empty visual element.
Yeah I understand and I think pooling is a great thing, but having option to use less performant behaviour, but more flexible I guess, would come in handy, especialy when extending editor window. Its just a thought tho, nothing that we couldnt live without ofc
the bindingPath is conflict with manual bindItem function. I want take the convenience of bindingPath, but also want to have bindItem to help me to process extra content like A label in ListItemView to show the index. How can I achieve this?