Revert "Asset Browser: Ensure parent catalogs are expanded when adding child"

This reverts commit 487faed6d0a1170a2f098552f794280fabe82186.

I changed my mind on how to implement this feature. Adding a catalog
should also activate it, like we do it for adding other data in Blender.
The activation will automatically make it visible then. See the
following commit.

1 files changed, 0 insertions, 11 deletions

diff --git a/source/blender/editors/include/UI_tree_view.hh b/source/blender/editors/include/UI_tree_view.hh
index 77472979beb..0d18eedeac9 100644
--- a/source/blender/editors/include/UI_tree_view.hh
+++ b/source/blender/editors/include/UI_tree_view.hh
@@ -196,15 +196,6 @@ class AbstractTreeView : public TreeViewItemContainer {
    * the actual state changes are done in a delayed manner through this function.
    */
   void change_state_delayed();
-  /**
-   * Typically when adding a new child from the UI, the parent should be expanded to make the new
-   * item visible. While this isn't totally bullet proof (items may be expanded where the child was
-   * added dynamically, not through user action), it should give the wanted behavior as needed in
-   * practice.
-   * "Focused" here means active or hovered, as a way to tell if the new item came from user
-   * interaction (on the row directly or through the context menu).
-   */
-  void unveil_new_items_in_focused_parent() const;
   void build_layout_from_tree(const TreeViewLayoutBuilder &builder);
 };
 
@@ -232,8 +223,6 @@ class AbstractTreeViewItem : public TreeViewItemContainer {
   bool is_open_ = false;
   bool is_active_ = false;
   bool is_renaming_ = false;
-  /* Could the item be identified from a previous redraw? */
-  bool is_new_ = true;
 
   IsActiveFn is_active_fn_;