Skip to content

Conversation

@RobertGlobant20
Copy link
Contributor

Purpose

Fixing the location of the engine label in the PythonScriptFromString node.
I've used the normal nodeView.grid for addnig the engineLabel instead of the nodeView.PresentationGrid due that this last one is located in a different row, column.

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
  • This PR contains no files larger than 50 MB

Release Notes

Fixing the location of the engine label in the PythonScriptFromString node.

Reviewers

@QilongTang

FYIs

Fixing the location of the engine label in the PythonScriptFromString node.
I've used the normal nodeView.grid for addnig the engineLabel instead of the nodeView.PresentationGrid due that this last one is located in a different row, column.
@RobertGlobant20
Copy link
Contributor Author

GIF showing the label in the expected place.
PythonScriptFromStringLabelFix

engineLabel.HorizontalAlignment = HorizontalAlignment.Left;
engineLabel.VerticalAlignment = VerticalAlignment.Bottom;
engineLabel.Margin = new Thickness(14, -4, -10, 4);
Canvas.SetZIndex(engineLabel, 5);
Copy link
Contributor

Choose a reason for hiding this comment

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

Are these similar to how Python Script node is setting the label location?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

yes, is almost a copy-paste.
image

@QilongTang QilongTang added this to the 2.19.0 milestone May 1, 2023
@QilongTang
Copy link
Contributor

The reported regression is a sporadic one

@QilongTang QilongTang merged commit 3103da5 into DynamoDS:master May 1, 2023
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.

2 participants