You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Here's an issue I have been experiencing for some time now but only now I am taking a minute to report about it.
Observed behaviour:
When annotating an image, if the cursor inadvertently moves out of the viewing/drawing area, the current shape stops "following" the cursor. Instead, the annotation is finalized using the last known cursor position within the viewer area as the final click.
Expected behaviour:
Annotations should only be finalized with a final click (or a double-click for ROIs). When annotating an image, the user expects the shape to follow their cursor until they click again (or double-click, if drawing an ROI). Moving the cursor out of the drawing/viewing area should not finalize the annotation. Instead, when the cursor returns to the viewing/drawing area, the shape currently being drawn should continue adjusting to the cursor's position.
How to reproduce:
I was able to reproduce this issue across multiple versions of DWV (up to the latest v0.34), using different images (e.g., baby MRI) and various annotation tools (ROI, rectangle, arrow, circle).
To reproduce:
Open the DWV demo and load the baby MRI dataset.
Select the Draw tool → Rectangle.
Click on the image to begin drawing a rectangle.
Move the cursor out of the viewer area (e.g., down to the button controls in the demo).
Expected: The rectangle corner should continue following the cursor. Actual: The rectangle follows the cursor until the moment the cursor exits the application area. At that point, it stops adjusting, and the last known cursor position inside the viewer is used to finalize the annotation. The annotation remains in this state until the user modifies it again by clicking on a node or on the rectangle itself.
I hope this is clear enough and that this helps. Please let me know if this needs more details. Thank you again for your great work.
Kind regards,
Greg
The text was updated successfully, but these errors were encountered:
Got it thanks. The behaviour is the expected one, I was not too sure what to implemented at the time. Now I see that what you describe is the behaviour of various other viewers so I'll switch to it. Thanks for reporting!
Hi @ivmartel ! I hope you are doing well.
Here's an issue I have been experiencing for some time now but only now I am taking a minute to report about it.
Observed behaviour:
When annotating an image, if the cursor inadvertently moves out of the viewing/drawing area, the current shape stops "following" the cursor. Instead, the annotation is finalized using the last known cursor position within the viewer area as the final click.
Expected behaviour:
Annotations should only be finalized with a final click (or a double-click for ROIs). When annotating an image, the user expects the shape to follow their cursor until they click again (or double-click, if drawing an ROI). Moving the cursor out of the drawing/viewing area should not finalize the annotation. Instead, when the cursor returns to the viewing/drawing area, the shape currently being drawn should continue adjusting to the cursor's position.
How to reproduce:
I was able to reproduce this issue across multiple versions of DWV (up to the latest v0.34), using different images (e.g., baby MRI) and various annotation tools (ROI, rectangle, arrow, circle).
To reproduce:
Expected: The rectangle corner should continue following the cursor.
Actual: The rectangle follows the cursor until the moment the cursor exits the application area. At that point, it stops adjusting, and the last known cursor position inside the viewer is used to finalize the annotation. The annotation remains in this state until the user modifies it again by clicking on a node or on the rectangle itself.
I hope this is clear enough and that this helps. Please let me know if this needs more details. Thank you again for your great work.
Kind regards,
Greg
The text was updated successfully, but these errors were encountered: