Just one example of a pretty common occurrence. Given the basic document structure below, where all items except the terminal leaf nodes (i, ii, iii, etc.) are Projects (headings) and all projects are populated all the way to leaves:
A
B
–1)
–2)
–3)
—-a
——i.
——ii.
—-b
——i.
——ii. <move this item>
–4)
–5)
C
D
etc.
I will be zoomed to B3b, and invoke “Move” on item B3bii.
The Move dialog prompts me with the following top-5 options:
- A
- B
- B1
- B1a, B1b, … all incomplete B1 subs
- B2
- B2a, B2b, … all incomplete B2 subs
- B3 (finally!)
- B3a, B3c, … etc.
Of course this is logical. Legend is just methodically drilling through all Project items in the heirarchy.
But for me (and I suspect others), I tend to want to move items between distal “twigs” – not root-level “branches”. If you’re working with a leaf in the last Project in your Outline and just want to move it to the next 2nd-tier branch over, the Move Dialog will make you scroll through basically your entire document’s worth of Projects (headings) before you’re even in the neighborhood.
I think the Move tool should prioritize the current lineage, drilling down as it does today but starting with the TL projects that lead directly to the selected item. Once that is exhausted, it should then present the remaining options as it does today. That would get the Move tool to where I can actually use it, and save time as a result. Today, I’m almost always better off opening a throwaway pane to drag/drop items instead.
