Skip to content

Conversation

@alxbilger
Copy link
Contributor

@alxbilger alxbilger commented Nov 17, 2025

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.

image

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

  • it builds with SUCCESS for all platforms on the CI.
  • it does not generate new warnings.
  • it does not generate new unit test failures.
  • it does not generate new scene test failures.
  • it does not break API compatibility.
  • it is more than 1 week old (or has fast-merge label).

@alxbilger alxbilger added pr: status to review To notify reviewers to review this pull-request pr: new feature Implement a new feature pr: highlighted in next release Highlight this contribution in the notes of the upcoming release labels Nov 17, 2025
@bakpaul
Copy link
Contributor

bakpaul commented Nov 19, 2025

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

@alxbilger
Copy link
Contributor Author

@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
Copy link
Contributor

epernod commented Nov 20, 2025

@alxbilger
Copy link
Contributor Author

@epernod thanks, I'll take it into account for a factorization

@alxbilger
Copy link
Contributor Author

[ci-build][with-all-tests]

@hugtalbot hugtalbot added this to the v26.06 milestone Dec 4, 2025
@hugtalbot hugtalbot added pr: status wip Development in the pull-request is still in progress and removed pr: status to review To notify reviewers to review this pull-request labels Dec 4, 2025
@alxbilger alxbilger force-pushed the visualmesh branch 2 times, most recently from 2e425a7 to b099b9e Compare December 10, 2025 15:19
@alxbilger alxbilger added pr: status to review To notify reviewers to review this pull-request and removed pr: status wip Development in the pull-request is still in progress labels Dec 10, 2025
@alxbilger
Copy link
Contributor Author

[ci-build][with-all-tests]

@alxbilger alxbilger force-pushed the visualmesh branch 3 times, most recently from 27e665c to 4b586c6 Compare December 18, 2025 07:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

pr: highlighted in next release Highlight this contribution in the notes of the upcoming release pr: new feature Implement a new feature pr: status to review To notify reviewers to review this pull-request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants