Skip to content

Conversation

@0xfedcafe
Copy link
Member

Describe your changes

Add support for temporal mesh in vtkF3DMemoryMesh and scene API. I haven't updated bindings yet as I haven't figured out which was to be updated or how.

Issue ticket number and link if any

#2443 , #2443

Checklist for finalizing the PR

  • I have performed a self-review of my code
  • I have added tests for new features and bugfixes
  • I have added documentation for new features
  • If it is a modifying the libf3d API, I have updated bindings
  • If it is a modifying the .github/workflows/versions.json, I have updated timestamp

Continuous integration

Please write a comment to run CI, eg: \ci fast.
See here for more info.

@github-actions
Copy link

You are modifying libf3d public API! ⚠️Please update bindings accordingly⚠️!
You can find them in their respective directories: python, java, webassembly.

@0xfedcafe
Copy link
Member Author

\ci fast

@0xfedcafe 0xfedcafe force-pushed the temporal-mesh-memory branch 2 times, most recently from 0454de1 to a89c03e Compare October 23, 2025 18:49
virtual scene& add(const std::filesystem::path& filePath) = 0;
virtual scene& add(const std::vector<std::filesystem::path>& filePath) = 0;
virtual scene& add(const std::vector<std::string>& filePathStrings) = 0;
virtual scene& add(const std::vector<mesh_t>& mesh, double timeStep) = 0;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

im not sure to follow, why is there multple meshes for a single timestep ?

@mwestphal
Copy link
Member

Need any help moving forward @0xfedcafe ?

@0xfedcafe 0xfedcafe force-pushed the temporal-mesh-memory branch from 47433bf to ff3de6e Compare November 6, 2025 14:51
@mwestphal
Copy link
Member

Hi @0xfedcafe , still working on this ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants