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
Draw effect does not take parent transform into account #4685
Comments
@Sunderlandkyl Could you please check how difficult would it be to fix this? |
Still looking at a fix, but this issue applies to both the draw and level-tracing effects. Edit: Also affects islands effect. |
Sunderlandkyl
added a commit
to Sunderlandkyl/Slicer
that referenced
this issue
Mar 27, 2020
The polydata for the draw effect was rasterized in the world coordinate system. If the segmentation node was under a transform node, the transform would not be taken into account when modifying the segment. This commit transforms the rasterized image to the same coordinate system as the segmentation before appending it to the modifier labelmap. re Slicer#4685
Sunderlandkyl
added a commit
to Sunderlandkyl/Slicer
that referenced
this issue
Mar 27, 2020
The polydata for the draw effect was rasterized in the world coordinate system. If the segmentation node was under a transform node, the transform would not be taken into account when modifying the segment. This commit transforms the rasterized image to the same coordinate system as the segmentation before appending it to the modifier labelmap. re Slicer#4685
lassoan
pushed a commit
that referenced
this issue
Mar 27, 2020
The polydata for the draw effect was rasterized in the world coordinate system. If the segmentation node was under a transform node, the transform would not be taken into account when modifying the segment. This commit transforms the rasterized image to the same coordinate system as the segmentation before appending it to the modifier labelmap. re #4685
Sunderlandkyl
added a commit
to Sunderlandkyl/Slicer
that referenced
this issue
Mar 27, 2020
The position of the mouse in IJK coordinates, as well as the position of the polydata did not previously take into account the parent transform of the segmentation. re Slicer#4685
Sunderlandkyl
added a commit
that referenced
this issue
Mar 27, 2020
The position of the mouse in IJK coordinates, as well as the position of the polydata did not previously take into account the parent transform of the segmentation. re #4685
lassoan
pushed a commit
that referenced
this issue
Mar 27, 2020
The position of the mouse in IJK coordinates, as well as the position of the polydata did not previously take into account the parent transform of the segmentation. re #4685
Fixed. |
Sunderlandkyl
added a commit
to Sunderlandkyl/Slicer
that referenced
this issue
Mar 28, 2020
The position of the mouse in IJK coordinates did not previously take into account the parent transform of the segmentation. re Slicer#4685
Sunderlandkyl
added a commit
that referenced
this issue
Mar 28, 2020
The position of the mouse in IJK coordinates did not previously take into account the parent transform of the segmentation. re #4685
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This issue was created automatically from an original Mantis Issue. Further discussion may take place here.
The text was updated successfully, but these errors were encountered: