Implementation of filtering TreeView may not be performant

[samamstar]

Current approach is to just collapse all widgets that don't match the filter, with the exception of parents that have a child that match, and vice versa.

Possible issue could arise where all objects in a view could end up getting displayed, since none of them match the filter. In a large data set this could cause significant performance issues.

For now; I'm leaving this on the backburner. If it becomes an issue in the future, here are some possible approaches:

• Stop returning children that don't match the filter in function "On_TreeWidget_BP_OnGetItemChildren_0" in LIB_WT_TreeView
  • may cause issues when filter is removed; will need to refresh list view in that case
• Don't bother with checks when test string gets more complex and we've already decided an object doesn't match
• Remove top-level objects that don't match
  • will likely cause similar issues to "Stop returning children" approach