When setting up input arguments for a Python Task while the Task Editor is open, the input arguments get deleted upon saving the task using the Task Editor's save button. This happens because the Task Editor creates a copy of the Python Task from the Process Data when it is opened. This copy does not reflect any changes made to the original Python Task stored in the Process Data. Consequently, if the Task in the Process Data is modified (e.g. input arguments are created) while the Task Editor is open, saving the Task through the Task Editor will overwrite the Process Data with the outdated copy.
Steps to Reproduce
- Open the Task Editor for a Python Task.
- While the Task Editor is open, modify the Python Task via the Properties Dock Widget.
- Return to the Task Editor and press the Save button.
- Notice that the property changes are lost after saving
When setting up input arguments for a Python Task while the Task Editor is open, the input arguments get deleted upon saving the task using the Task Editor's save button. This happens because the Task Editor creates a copy of the Python Task from the Process Data when it is opened. This copy does not reflect any changes made to the original Python Task stored in the Process Data. Consequently, if the Task in the Process Data is modified (e.g. input arguments are created) while the Task Editor is open, saving the Task through the Task Editor will overwrite the Process Data with the outdated copy.
Steps to Reproduce