-
Notifications
You must be signed in to change notification settings - Fork 343
[Visual] Introduce generic visualization of mesh #5782
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
|
I like very much the idea, it goes along with what you already did in recent PR. but I would like this to be factorize with the code for drawing introduced here : #5636 Plus, we should (in another PR of course) remove all drawing from all topology object that currently exist if any |
|
@bakpaul I did not think about the GUI. In your opinion, does a component still make sense if the GUI allows to visualize the mesh? |
|
@epernod thanks, I'll take it into account for a factorization |
104f87b to
92e3604
Compare
|
[ci-build][with-all-tests] |
2e425a7 to
b099b9e
Compare
|
[ci-build][with-all-tests] |
27e665c to
4b586c6
Compare
Introduce a set of classes to draw a mesh (from triangles, tetrahedra or hexahedra). Those classes can then be used everywhere such a mesh is drawn, such as in force fields.
Introduce a component to visualize a mesh. This component is designed to draw surface and volume meshes, in the similar manner it is done in the debug drawing of current force fields.
Finally, the draw classes are also used to draw objects when selected in the GUI.
By submitting this pull request, I acknowledge that
I have read, understand, and agree SOFA Developer Certificate of Origin (DCO).
Reviewers will merge this pull-request only if