-
Notifications
You must be signed in to change notification settings - Fork 635
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Do not set execution hint on undo move #11519
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -189,9 +189,12 @@ public bool UsingDefaultValue | |
get { return usingDefaultValue; } | ||
set | ||
{ | ||
usingDefaultValue = value; | ||
RaisePropertyChanged("UsingDefaultValue"); | ||
RaisePropertyChanged("ToolTip"); | ||
if (usingDefaultValue != value) | ||
{ | ||
usingDefaultValue = value; | ||
RaisePropertyChanged("UsingDefaultValue"); | ||
RaisePropertyChanged("ToolTip"); | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I like the fix here. Also curious does similar problem not exist for other properties, e.g. X, Y etc? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yes, this pattern is used in most places. For |
||
} | ||
} | ||
} | ||
|
||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -347,7 +347,14 @@ protected override void DeserializeCore(XmlElement nodeElement, SaveContext cont | |
|
||
if (engineNode != null) | ||
{ | ||
this.Engine = (PythonEngineVersion)Enum.Parse(typeof(PythonEngineVersion),engineNode.InnerText); | ||
var oldEngine = Engine; | ||
Engine = (PythonEngineVersion)Enum.Parse(typeof(PythonEngineVersion), engineNode.InnerText); | ||
if (context == SaveContext.Undo && oldEngine != this.Engine) | ||
{ | ||
// For Python nodes, changing the Engine property does not set the node Modified flag. | ||
// This is done externally in all event handlers, so for Undo we do it here. | ||
OnNodeModified(); | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 👍🏻 |
||
} | ||
} | ||
} | ||
|
||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @mmisol Did you test that downstream node can be also reverted back to the previous state?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure I follow. Could you mention the steps of the test?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure, if a node is frozen, the downstream nodes are also frozen. The original code seems taking care of correctly marking downstream nodes when undo freezing node as well. Just want to make sure the behavior is the same.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh ok. Yes, I tested that and it works