Skip to content
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

Fix Regression with GetCLRObject impacting Node Preview and Tessellation #13363

Merged
merged 2 commits into from
Sep 30, 2022

Conversation

saintentropy
Copy link
Contributor

Purpose

This fix addresses a regression found in Dynamo 2.16 related to the preview bubble and tessellation for the background preview. After installing a package during a session both would stop working correctly. This appears to be relates to changes introduced in #12934 and #11920. This PR reverts the behavior to the previous code.

Declarations

Check these if you believe they are true

  • The codebase is in a better state after this PR
  • Is documented according to the standards
  • The level of testing this PR includes is appropriate
  • User facing strings, if any, are extracted into *.resx files
  • All tests pass using the self-service CI.
  • Snapshot of UI changes, if any.
  • Changes to the API follow Semantic Versioning and are documented in the API Changes document.
  • This PR modifies some build requirements and the readme is updated

Release Notes

Corrects regression in Dynamo where after installing a package during a session the node preview bubble and background preview would not operate correctly.

Reviewers

@mjkkirschner

FYIs

@aparajit-pratap @QilongTang @pinzart

@saintentropy
Copy link
Contributor Author

saintentropy commented Sep 30, 2022

@mjkkirschner mjkkirschner self-requested a review September 30, 2022 20:44
This was referenced Sep 30, 2022
//checks for this edge case by verifying that the requested StackValue pointer is associated with an
//imported library. An example is the "Function" pointer which does not have an associated CLRObject.
//In that case, the return value should be null.
var classNode = runtimeCore.DSExecutable.classTable.GetClassNodeAtIndex(svData.metaData.type);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I believe GetClassNodeAtIndex was also introduced as part of the previous fixes. I suppose it's no longer needed as this line of code has been removed. Can the function, therefore, be removed?

Copy link
Contributor Author

@saintentropy saintentropy Sep 30, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yep it can be... I will file a follow up to re-look at this optimization. And we can either to fix the optimization or clear up that function too

@mjkkirschner
Copy link
Member

Let's also wait to merge this until tests pass as I see tests were added in the linked prs.

@mjkkirschner
Copy link
Member

@mjkkirschner mjkkirschner merged commit f50c788 into DynamoDS:master Sep 30, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants