-
Notifications
You must be signed in to change notification settings - Fork 326
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
Fix/crosshairs annotations #303
Conversation
sedghi
commented
Nov 19, 2022
•
edited
Loading
edited
- Make Crosshairs to remove their annotations upon disabled
- Make annotation rendering engine to reset its rendering flags when a viewport is removed
✅ Deploy Preview for cornerstone-3d-docs ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
84db1e1
to
26b125d
Compare
@@ -210,6 +210,7 @@ class RenderingEngine implements IRenderingEngine { | |||
|
|||
// 5. Remove the requested viewport from the rendering engine | |||
this._removeViewport(viewportId); | |||
viewport.hasBeenDisabled = true; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The naming here is very odd, and I think it ends up not being quite right. hasBeenDisabled doesn't mean it is currently disabled, but suggests that at some point in the past it got disabled. Is it safe to say:
viewport.isDisabled = true
or
viewport.disabled = true
Otherwise, what about making it more prescriptive, something like disableOverlayDrawing, so that it is specifying that no overlays are to be drawn this viewport, and that would include things like the crosshairs, but may also include things like segmentation overlays etc.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Makes sense
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good now.
* feat: add hasBeenDestroyed to viewport and fix bugs * fix: reset annotation render on remove element * new api * apply review comments
…303) * feat(anonymizer) - export Array tagNamesToEmpty and add parameter in function cleanTags -> manage the tags to anonymize/modify in dicom * fix comma * return a copy of the list tagsNameToEmpty and then pass in the lists as optional arguments to cleanTags Co-authored-by: CASTELNEAU Julien <[email protected]>