You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the current implementation, the workflow is reinstantiated every time there is a change in the GUI. The associated code snippet can be found in reactflow.py:
Besides caching becoming non-functional, wf.save also does not work. This is probably due to the reinstantiation trying to add children with the same label to an already saved workflow. The GUI itself simply becomes unresponsive at this point.
While the reinstantiation is a clean way of capturing changes from the GUI side of things, I think it is leading to too many loses in functionality. It would perhaps be better to break down the get_workflow function so that changes are handled without reinstantiating the workflow.
Thoughts @pyiron/gui? (just testing out the teams functionality here, please ignore if you don't want to contribute to the issue)
The text was updated successfully, but these errors were encountered:
In the current implementation, the workflow is reinstantiated every time there is a change in the GUI. The associated code snippet can be found in
reactflow.py
:Besides caching becoming non-functional,
wf.save
also does not work. This is probably due to the reinstantiation trying to add children with the same label to an already saved workflow. The GUI itself simply becomes unresponsive at this point.While the reinstantiation is a clean way of capturing changes from the GUI side of things, I think it is leading to too many loses in functionality. It would perhaps be better to break down the
get_workflow
function so that changes are handled without reinstantiating the workflow.Thoughts @pyiron/gui? (just testing out the teams functionality here, please ignore if you don't want to contribute to the issue)
The text was updated successfully, but these errors were encountered: