While it's not elegant having to pop into the Preferences panel to adjust "Maximum tree search depth" (it can be torn off), I do get quite a bit of mileage from this one setting. It basically lets me switch between Filter, Navigate and Search[2+] use cases as needed, but with a clarity about how it is actually going to do them (traversal depth) that is easily understood.
I do have to be extra careful with anything over 1 when exploring a high-level Magma object with proxies out into a huge repository because, with no way to abort, an accidental key press can become a frustrating image-lock.
Getting Filter working better would also make it feel better. Depth of 0 should just filter the selected items siblings, (and, if that causes a mismatch on the selected item, changing the selection), but without affecting their expanded/unexpanded status of anything.
 -- (Filter) I have a collection with 8000 elements, I want to filter the list without changing expanded state of anything. (Currently doesn't work)
 -- (Navigate) I just explored a Morph and quickly want to navigate to 'extension' -> 'otherProperties' -> 'layoutPolicy' -> 'properties'. (Works!)
[2+] -- (Search) I'm looking for a data value, but don't know where it is, let the machine do the work.
Well, if you would filter siblings first, the object explorer would be a little bit harder to use with its single 1st-level-item ("root"). But yes, go ahead and change it and we will play around with it and evaluate it until the next release. :)
P.S.: It is still a good idea to select the "root" node in the object explorer and _NOT_ its first child if any. Just to clarify. :-)
|Free forum by Nabble - Resume Templates||Edit this page|