Aye, it seems so. The thing is that you do not need to push in a base uObject. You can push whatever you want as Item, providing it inherits from uObject, and everything does. Hence the need for casting. If you have a bunch of actors, pawns, or something with deep inheritance chain, you can actually use that instead of the additional uObject. As in:
I just don’t understand why the Entry Widget Class could not also act as a the carrier of the data, instead of being separated just to take care of the graphical interpretation of the List View entry.
Seconded and agreed - I’d like to push in a struct (by reference!) please! @Epic