OXIDE Trees
Last updated
Last updated
OXIDE uses a number of "tree views" to represent things like the views in the app, the files in a CloudCode task and more.
OXIDE trees, for the most part, will retain their state when nodes (folders) are collapsed or expanded. This means that when switching across views or working with the tree directly, nodes which have been expanded/collapsed will retain their state even when their parent state changes. See more info below for some more advanced interactions with trees.
Most tree views in OXIDE can be searched. When a tree has a search box above it, you can search it in a nested manner (search is case-insensitive):
While searching, all nodes in the tree will be locked to an expanded mode to show the full extent of the search. As can be seen in the image, a folder will still be listed if it happens to have children that match the search term.
To completely expand a tree from a specific node, hold down the [alt] key and click on a collapsed node. The node will auto expand all of its children:
The same can be done for a node which is already expanded. Holding down [alt] and clicking on a collapsed node will collapse all nested children (see the section on retaining tree state above for why this happens)
