-
Notifications
You must be signed in to change notification settings - Fork 334
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
[Bug] Brushing Feature Malfunction When Switching Active Segments in THRESHOLD_INSIDE_CIRCLE strategy #1724
Comments
is this still happening? |
@sedghi |
@sedghi You can still reproduce this issue by replacing |
Hi @sedghi , |
I have a PR i wonder if it solves it #1820 |
Describe the Bug
When using the
THRESHOLD_INSIDE_CIRCLE
strategy for brushing and switching the active segment from one to another, the brushing feature does not function as expected.To illustrate the issue, I have modified the example code for
segmentationVolume
and prepared a reproducible case. stada526#2Since the behavior is complex and difficult to describe accurately, please refer to the steps to reproduce below and the attached video.
(Note that these features used to function properly in Cornerstone.js v1)
Steps to Reproduce
Using my modified code stada526#2:
1. Click “Load DICOM”.
2. Click “Create Empty SEG” (let’s call it “segment1”).
3. Draw a segment.
4. Click “Create Empty SEG” again to create another segment (let’s call it “segment2”).
5. Draw a segment (the “segment2” will not be displayed).
6. Select “segment1” from the dropdown menu.
7. Draw a segment (the segment will not be displayed, but the “segment2” that wasn’t drawn in step 5 will now appear).
When using the normal brush mode by passing the
BrushTool.toolName
tosetToolActive
, this issue doesn't occur.2024-12-20.12.30.26.mov
The current behavior
A newly drawn segment will not be displayed after switching the active segment.
The expected behavior
A newly drawn segment will be displayed even after switching the active segment.
OS
maxOS 15.1
Node version
v21.7.1
Browser
Chrome 130.0.6723.117
The text was updated successfully, but these errors were encountered: