Widget Variables become invalid

Development Programming & Scripting Blueprint
, , , , , ,
2

Continued from the previous thread - you’re still not using the List View correctly.

The functionality of those specialised containers revolves around the underlaying objects holding data - the widgets are just fluff on top pulling the data out of the objects. For example, nowhere in your script above are you using the Interface the List View widgets must implement.

Consider the following:

image

  • the CustomPrimaryDataAsset holds some data we’d like widgets have access to
  • the ListViewObject is the the data the native List View operates on and uses to create widgets below
  • the wListViewEntry are the widgets generated automatically by the native List View, they will pull data from the ListViewObject - the interface is implemented here
  • the ListViewOwner is the widget that holds the native List View

List View Object

Exposing variable pins makes the blueprint flow clearer:

image
image1079×433 46.2 KB

image
image2321×468 174 KB

Above when the widget holding the native List View is added to the viewport, we create ListViewObjects and feed them data via the exposed parameters. No need for additional custom events and wires.

List View Entry

When a List View automatically generates its wListViewEntries, it will deliver the underlaying objects via the interface:

image
image1950×445 161 KB