Use of BaseViewer selection mechanism to add live selection feedback in the 3D view #18
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.


During discussion about the removal of every showXXX in object (as in sofa-framework/sofa#5591) it was pointed that having display component in the scene cover one use case... but not the "scene" debugging one, so as asked by @hugtalbot, here is a draft of live "showXXX" implemented "out of the scene".
For the moment this is just for drafting as there is a lot to do in a different way, especially the rendering of the different type of objects. In the PR, it is based on the data field's name and dynamic_cast... (see drawSelection method). This is clearly a questionable design. Moving all this code in Sofa.Gui.Common is probably to consider because the "selection" rendering code & logic can/may/should be shared by all the GUIs instead of implemented in each of them.
To activate use the -i (interactive) mode is on, so no consequences for default uses.
Possible things to do to move forward:
A Small video:
