Now that we can select such things from the text window, perhaps a selection of multiple items could could make the items in question also selectable in the text window, with the option of de-selecting ? That way, an ambiguous selection could just select everything applicable, and the user could get rid of the undesired bits.

Another way for handling ambiguous selections that works quite nicely (but would require some changes to the selection logic if applied to SolveSpace) is something I've implemented in fped:

• first, make a list of the candidates, sorted roughly by the difficulty of catching the respective item,
• tentatively select the one that's hardest to catch,
• if clicking again on the same selection, pick the item after the one currently selected,
• and so on.

We even should already have the list of entities under cursor.

This even was already implemented as "select by order"

I'm not sure if that's the best UI really, compared to e.g. listing all entities in the text window. I'll need to think about it.

Evil-Spirit/solvespace@a7be019

@Leichtbier and @wpwrak There is a pending pull request to give preference to non-construction lines when selecting entities ( #810 ). What do you think of that? Would that be better than having the current behaviour which seems more random?

FYI It is now possible to pick coincident lines by slightly rotating the sketch. For depth comparison each line is considered to be at the depth of its midpoint. That means if you rotate the sketch a little bit it will select the "closest" line when they overlap.

Current master also has the exploded view for 2d sketches, which separates all lines by an adjustable interval perpendicular to the sketch plane.

I'm going to close this, as the exploded view should cover it. There have been other improvements to selection since this was opened as well, and there has been no feedback on any of that.