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

Set Location Based on Other #16

Open
MarkAckerley opened this issue Apr 5, 2019 · 5 comments
Open

Set Location Based on Other #16

MarkAckerley opened this issue Apr 5, 2019 · 5 comments

Comments

@MarkAckerley
Copy link

MarkAckerley commented Apr 5, 2019

  • Workflow Information: Dynamo File Name: Viewport Set Location Based On Other

  • I'm submitting a ... Bug report

  • Do you want to request a feature or report a bug? Report a bug

  • What did you see? Viewports did not align

  • What did you expect (or want to) see? Viewports did align

  • What is the motivation / use case for changing the behavior? To have aligned viewports

  • Other information If the Annotation crop is set to false, the viewports align. It would be great if the node could note the current state, set it to false, then return it to the previous state once the viewports were aligned.

Test123

@johnpierson
Copy link
Owner

Ooh. I like it. I can add that to the workflow. Do you see any potential issues with toggling that right off hand? I remember it used to have a bug where it would reset grids if you had jogged them.

@MarkAckerley
Copy link
Author

Umm... Not that I know of... Apologies if it makes your node worse :(

@johnpierson
Copy link
Owner

LOL, I will do some testing before release!

@MarkAckerley
Copy link
Author

Thanks John, I feel guilty for giving you more work... Let me know if I can help at all.

@johnpierson
Copy link
Owner

No worries at all man. Pointing out suggestions like this is great.

Full Disclosure: Rhythm is primarily in a mode of bug fixes and version updating. I rarely add new features any longer and focus on fixes.

This is definitely a worthy fix as it can fix some of the unexpected results!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants