fix(imagereslicemapper): be less sensitive for "snapping" to nearest … #3159
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…orthogonal axis
When using the vtkImageResliceMapper in conjunction with the ResliceCursorWidget(RWC), there was a case when the RCW lines were displayed partly being the slice when the slice plane was being snapped to the nearest orthogonal axis.
Context
When rotating the ResliceCursorWidget near an orthogonal axis, the RCW line was being displayed partly in front of the slice and partly behind the slice. This is because the slice was snapped to the nearest orthogonal axis.
Changes
PR and Code Checklist
npm run reformat
to have correctly formatted codeTesting