Skip to content
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] Measurement Selection Not Switching Series in 2D MPR View #4751

Open
Jaseel-trenser opened this issue Jan 31, 2025 · 0 comments
Open
Assignees
Labels
Awaiting Reproduction Can we reproduce the reported bug?

Comments

@Jaseel-trenser
Copy link
Contributor

Describe the Bug

When an annotation is created in the first series, then the second series is loaded, clicking on the measurement of the first series in the measurement panel does not switch back to the corresponding series in the 2D MPR view.
It is also noted that if two series in a session have different FrameOfReferenceUID, the series switches as expected when clicking a measurement from the measurement panel

2025-01-31_12-02-30.mp4

Steps to Reproduce

  1. Launch a multi-series study with the same FrameOfReferenceUID.
  2. Draw an annotation on the first series.
  3. Navigate to MPR mode.
  4. Drag and drop the second series into MPR mode.
  5. Click on the annotation of the first series from the measurement panel.
  6. Observe the viewport - the series does not switch back to the first series.

The current behavior

The series is not switching; instead, the annotation appears as a dashed line in the currently loaded series

The expected behavior

When clicking on a measurement, the corresponding series should load and navigate to the slice containing the annotation

OS

Windows 11

Node version

20

Browser

Chrome

@Jaseel-trenser Jaseel-trenser added the Awaiting Reproduction Can we reproduce the reported bug? label Jan 31, 2025
@linear linear bot assigned sedghi Jan 31, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Awaiting Reproduction Can we reproduce the reported bug?
Projects
None yet
Development

No branches or pull requests

2 participants