# History Tree 'invert option'

**URL:** <https://discourse.shapr3d.com/t/history-tree-invert-option/34804>\
**Category:** Feature requests\
**Created:** [October 12, 2024, 4:47pm UTC](https://discourse.shapr3d.com/t/history-tree-invert-option/34804 "2024-10-12T16:47:00Z")\
**Posts on this page:** 1\
**Showing post:** 22

<div class="post-metadata">

**Author:** ![BKE](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.shapr3d.com/bke/32/31690_2.png) [@BKE](https://discourse.shapr3d.com/u/BKE)\
**Post date:** [June 6, 2025, 11:07am UTC](https://discourse.shapr3d.com/t/history-tree-invert-option/34804/22 "2025-06-06T11:07:12Z")

</div>

Another related crosspost

As I work, or is at least aimed at working, organized and also usually export to other systems and renderers, I would benefit from the following. And maybe some other well-structured mind could find it useful.

(Besides a description of items and their purpose I include a code for material as most render machines can search and replace texture/materials in incoming .x\_b., this would also benefit export-import of visualized parts in S3D.)

1. A search of text in items list, preferably high-lightning all matches (and open the parent tree).

2. A connected possibility to hide/hide others of the matches.

3. Following ability to select matches in visualization.

To this, a GREP/REGEX search would an extra topping.

(Nag nag; do \_not \_collapse expanded hierarchy at closing project, and let us use the alt-click (macOS standard) or iOS long-click, to completely open/collapse a tree branch.)

Edit: sorry, wrong thread, but I let it stand…

---

_[View the full topic](https://discourse.shapr3d.com/t/history-tree-invert-option/34804)._