Skip to content

Conversation

@dragos-ana
Copy link
Collaborator

This commit fixes two bugs related to #29:

  • The render window can only be initialized only once per session in the current setup, otherwise there is no proper binding to the new render window. This can be easily checked by switching to a new input file in the current state of the tool - the geometry of the previous file is still displayed. This commit fixes the underlying issue by only initializing the render window if it was not saved on the server side.
  • Also, there was a non-existent function used for the determination of the current material, such that the material selection was not displayed correctly. This is fixed as well.

Interested parties: @LaSi5002, @c-p-schmidt

@dragos-ana dragos-ana self-assigned this Nov 11, 2025
Copy link
Contributor

@c-p-schmidt c-p-schmidt left a comment

Choose a reason for hiding this comment

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

Looks good. But the formatting is broken according to the pipeline.

- The render window can only be initialized only once
per session in the current setup, otherwise there is no
proper binding to the new render window. This can be easily
checked by switching to a new input file in the current
state of the tool. This commit fixes the underlying issue
by only initializing the render window if it was not saved
on the server side.
- Also, there was a non-existent function used for the
determination of the current material. This is fixed as well.
@dragos-ana dragos-ana force-pushed the bugfix-render-window-creation branch from 7803619 to 47a31b2 Compare November 11, 2025 09:37
@dragos-ana dragos-ana enabled auto-merge November 11, 2025 09:39
@dragos-ana dragos-ana merged commit bb5d38a into 4C-multiphysics:main Nov 11, 2025
2 checks passed
@LaSi5002
Copy link
Contributor

The master_material_ind actually should not be set at all, because the highlighted material is now handled in update_pyvista_render_objects()

@dragos-ana
Copy link
Collaborator Author

dragos-ana commented Nov 11, 2025

That's true, thanks! Please remove this yourself in the upcoming PR since this PR is already merged, and the small deletion does not require a separate PR

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants