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] Image Manipulation Resets After Progressive Load in Stack Viewport #4747

Open
kushgadhvi16 opened this issue Jan 30, 2025 · 1 comment
Labels
Awaiting Reproduction Can we reproduce the reported bug?

Comments

@kushgadhvi16
Copy link

kushgadhvi16 commented Jan 30, 2025

Describe the Bug

This issue occurs when using progressive load with a stack viewport. The expected behaviour is that any applied image manipulations (such as window/level, zoom, and pan) should persist after an image is updated from lossy to lossless. However, all transformations are reset, requiring the user to reapply them manually. The same behaviour is observed when scrolling through images in the stack viewport—each new image load resets all transformations.
This is because, in StackViewport, for _updateActorToDisplayImageId function sameImageData is coming as false since lossy and lossless have different rows and columns.

Steps to Reproduce

  1. Enable progressive load in the OHIF viewer.
  2. Apply any image manipulations (WW/WL, zoom, pan).
  3. Changes are rested when the image changes from lossy to lossless or when scrolling to slices.

The current behavior

Manipulation is rested when scrolling or when the image is changed from lossy to lossless.

The expected behavior

Manipulation like WW/WL zoom pan should be retained.

OS

macOS 15.1.1

Node version

20.18.1

Browser

Chrome

@kushgadhvi16 kushgadhvi16 added the Awaiting Reproduction Can we reproduce the reported bug? label Jan 30, 2025
Copy link
Member

sedghi commented Feb 4, 2025

I think i know what is going on. We should getPresentation and setPresentation after update. Do you have reproducible example?

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