Revisit spec for LHS hit navigator search

[phraenquex]

Use cases:

• LHS search by substring match to shortcode, compound ID and/or alias #1563
• any of the strings in the extended observation view (incl. full path)
• Search by substructure and/or similarity - SMILES or 2D sketcher
• Search by 3D location: centre of NGL; last-selected atom
• (to be extended)

Spacer

(The original ticket entries don't match the ticket title: the thing below the line, and the two Mar 6/7 entries.)

---

This snapshot even recreates the search string (CX1134B) - but the LHS list doesn't shrink down to just that hit (the behaviour I expected/remembered).

https://fragalysis.xchem.diamond.ac.uk/viewer/react/projects/26/26

[boriskovar-m2ms]

This unfortunately works as designed. So many hits are visible in the hit navigator because they're visible in the NGL View. The rules for visibility and ordering of the LHS are so complicated that even I need to painstakingly debug the code to find out it's behaving in line with spec. For normal end user the behavior seems buggy or random at best. There is even a ticket somewhere, where the need to for some kind of simplification or maybe some feedback why hit is displayed to the user is described but I'm not able to find it.

[phraenquex]

First thing: give visibility to user to why something is on there. e.g. give a eye-type icon which will reveal that.

May well be superceded by #1322