Implicit triggerRender

[xhluca]

I feel the triggerRender is a bit clunky and makes it impossible to have more than one callback that updates a given view. how much effort would it be to make that implicit?

EDIT: Ok so it already works with the trigger render, so let's remove it from the demos:

• usage-vtk-cfd
• slice-rendering
• [ ]

[xhluca]

For example, the following approach would not work:

@app.callback(
  [Output("vtk-view", "triggerRender"), Output("mesh", "value")],
  [Input(...)]
)
def update_mesh_nested_in_view(...):
    ...

@app.callback(
  [Output("vtk-view", "triggerRender"), Output("algorithm", "value")],
  [Input(...)]
)
def update_algorithm_nested_in_view(...):
    ...

Since dash doesn't allow having an output being shared across different callbacks. However with an implicit rendering trigger it wouldn't have this problem.

[jourdain]

It is already the case... You can remove such output

[xhluca]

@jourdain you are right. i'll update the issue as a reminder to remove those from the tutorials/demos since it's legacy.

[xhluca]

@jourdain Actually, seems like it's not true for all cases.

With the F1 vehicle geometry app, it seems like it doesn't work when we try to set the visibility, but it only works when we update the mesh color.

Without the triggerrender:

With the trigger render:

[jourdain]

That is an easy fix... I'll do it tomorrow

[jourdain]

react-vtk-js@1.4.3 should fix that if you update dash_vtk tomorrow morning before I start my work...

[xhluca]

I haven't tried this but it doesn't seem to be a problem anymore. Will close it but if it comes back in the future we can reopen

[MuntherOdeh]

Hi, I've tried the code app.py but it's still not working with or without the trigger render. It gives me everytime the same error:
Callback error updating vtk-view.triggerRender