-
Notifications
You must be signed in to change notification settings - Fork 455
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
Feature: add orientation markers tool #1089
Conversation
Codecov Report
@@ Coverage Diff @@
## master #1089 +/- ##
=========================================
Coverage ? 17.83%
=========================================
Files ? 274
Lines ? 8428
Branches ? 1420
=========================================
Hits ? 1503
Misses ? 5759
Partials ? 1166
Continue to review full report at Codecov.
|
@frolic06 is this ready for review? |
Yes |
@dannyrb did you have to review this PR ? |
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.
- Thanks for creating an example page
- The new tool's implementation looks good 👍
- A couple of small comments that need to be addressed before merge.
- It would be nice if you could add this to our netlify example as an "overlay" tool, and give the example images any meta they may need to render orientations markers.
Thanks for your hard work on this, @frolic06! ^_^ |
🎉 This PR is included in version 4.5.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Feature
What is the current behavior? (You can also link to an open issue here)
No
What is the new behavior (if this is a feature change)?
It adds a tool called OrientationMarkersTool, which displays orientation markers like in version 2.X
Some code:
const orientationMarkers = cornerstoneTools['OrientationMarkersTool'];
cornerstoneTools.addToolForElement(element, orientationMarkers);
cornerstoneTools.setToolActiveForElement(this.element, 'OrientationMarkers', {});
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
No
Other information: