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
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The Python node's code editor sends an UpdateModelValueCommand with an empty workspace GUID, meaning the current workspace. Since the Python editor is no longer modal, this assumption (that the parent workspace is current) no longer holds. This change explicitly provides the workspace ID. This fixes#9479, avoiding a crash when a modeless Python node editor is opened from a custom node workspace and "Run" or "Save" is clicked while the home workspace is current.
Need to add a test for #9479 and confirm that the API change to add a parameter to the internal method ScriptEditorWindow.Initialize doesn't violate our API policies.
Dewb
changed the title
Python node should provide a workspace ID when updating model
Python script editor should provide a workspace ID when updating model
Sep 18, 2019
The reason will be displayed to describe this comment to others. Learn more.
@Dewb In this case, can you make a comment to the class, e.g. TODO: Make this class internal in Dynamo 3.0? By the time we tackle it, we would remember to do this.
DynamoDS#9988)
* Python node should provide a workspace ID when calling UpdateModelValueCommand, fixing DynamoDS#9479
* Draft test for DynamoDS#9479 (not passing yet due to undo issues)
* Disable section of python custom node save test that uses undo
* Remove file added by accident
* Fix null dereference in UpdateModelValueImpl
(cherry picked from commit e775794)
#9988) (#10173)
* Python node should provide a workspace ID when calling UpdateModelValueCommand, fixing #9479
* Draft test for #9479 (not passing yet due to undo issues)
* Disable section of python custom node save test that uses undo
* Remove file added by accident
* Fix null dereference in UpdateModelValueImpl
(cherry picked from commit e775794)
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Purpose
The Python node's code editor sends an UpdateModelValueCommand with an empty workspace GUID, meaning the current workspace. Since the Python editor is no longer modal, this assumption (that the parent workspace is current) no longer holds. This change explicitly provides the workspace ID. This fixes #9479, avoiding a crash when a modeless Python node editor is opened from a custom node workspace and "Run" or "Save" is clicked while the home workspace is current.
Declarations
Check these if you believe they are true
*.resxfiles