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

"Harden transform" on ROI is incorrect when tfm has rotation #1636

Closed
slicerbot opened this issue Mar 12, 2020 · 3 comments
Closed

"Harden transform" on ROI is incorrect when tfm has rotation #1636

slicerbot opened this issue Mar 12, 2020 · 3 comments
Assignees
Labels
Priority: Medium Issues that we plan to fix but there are available workarounds Type: Enhancement Improvement to functionality
Milestone

Comments

@slicerbot
Copy link
Collaborator

This issue was created automatically from an original Mantis Issue. Further discussion may take place here.

@lassoan
Copy link
Contributor

lassoan commented Mar 18, 2020

When ROIs will be ported from annotations to markups module, they will support arbitrary orientation.

@lassoan lassoan added Priority: Medium Issues that we plan to fix but there are available workarounds Type: Enhancement Improvement to functionality labels Mar 18, 2020
@lassoan lassoan added this to the Backlog milestone Mar 18, 2020
@lassoan lassoan mentioned this issue Jul 25, 2020
42 tasks
@lassoan
Copy link
Contributor

lassoan commented Mar 4, 2021

Markups ROI can be transformed nicely, but when the transform is applied then the ROI changes. There should be no visible change in the ROI when the transform is hardened

@lassoan
Copy link
Contributor

lassoan commented Jul 26, 2021

Works well in current Slicer Preview Release (Slicer-4.13.0-2021-07-25).

@lassoan lassoan closed this as completed Jul 26, 2021
@lassoan lassoan modified the milestones: Backlog, Slicer 4.13.0 Jul 26, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority: Medium Issues that we plan to fix but there are available workarounds Type: Enhancement Improvement to functionality
Development

No branches or pull requests

3 participants