DYN-6518 - Cherry Picks for 2.19.5#15019
DYN-6518 - Cherry Picks for 2.19.5#15019saintentropy wants to merge 2 commits intoDynamoDS:RC2.19.5_masterfrom
Conversation
|
The pull request SelfServe results does not seem real, maybe ASM or libG related errors? Other than that looks good |
| selectedString = GetSelectedStringFromItem(Items.ElementAt(value)); | ||
| } | ||
|
|
||
| OnNodeModified(); |
There was a problem hiding this comment.
I believe the fix for one of those two issues in 3.0 caused an issue in Revit ( REVIT-217658 ) where a custom dropdown node of an internal-package for DynamoRevit that needed to update on idle was stuck always one update state delayed, sometimes leading to confusing situations where Dynamo Player showed content from the previously opened Revit model.
We might want to consider the risks/benefits of this change, and if we will backport this change into 2.19 then in Revit we must also integrate the changes for REVIT-217658. We should also test around nodes that have UI updates to make sure there aren't other issues not yet found.
|
@saintentropy @twastvedt Close this PR? |
|
Closing (won't cherry pick for 2.19) due to the resulting bugs referenced by Vlad above. |
Purpose
This Cherry Pick is bring in #14656 and #14744. These two PR's addressed a regression in behavior for some DropDown nodes in Revit introduced in 2.19.0 and fixed in 3.0.
This original regression was related to this PR #14122
Declarations
Check these if you believe they are true
*.resxfilesRelease Notes
Some Drop down nodes had issues when Dynamo is set to Automatic Run Mode in DynamoForRevit. This change addresses this issue.
Reviewers
@twastvedt @BogdanZavu
FYIs
@Mikhinja @aparajit-pratap @QilongTang