ensure the ScopePath::navigate() implementation can handle context dependent paths

[Ichthyostega]

the basic idea is to build some context sensitivity into the "parent discovery" query. Especially (that's the key point), a root track scope should see the timeline or meta-clip it's bound into as his parent -- and this "seeing the parent" obviously is context and state dependent. A new ScopePath created targeting a given Scope would pick up the path according to the current query focus (context). Especially, this path will descend from root through the same timeline - sequence binding, which was used to reach the current focus location.

Verify this scheme actually works...

• with the ScopePath::navigate()-function
• with the relevant query or discovery functions on QueryFocus (which in turn are used to implement any dedicated navigation functions on individual model types.

[Ichthyostega]

after reconsidering that, I don't think it's a clever idea to put this functionality into the parent discovery. Rather, we should try to keep separated the "physical" / "logical" view on the scopes. It rather looks like this belongs directly into ScopePath

[Ichthyostega]

I've now analysed the whole situation. It turns out that either navigate() or a special query function on QueryFocus might be used to centralise the logic to provide such an virtual/effective tree structure (which we need when starting to implement meta-clips). And yes -- the implementation currently in code is not up to the job...

[Ichthyostega]

settled now for the extension point to be in ScopePath::navigate()

Currently, this function just returnes the raw path....

[Undercover Agent]

Migration MasterTickets ⟼ Subtickets-plugin