Skip to content

Conversation

@lchauvin
Copy link
Contributor

Related to #610

@netlify
Copy link

netlify bot commented Jun 19, 2024

Deploy Preview for volview-dev ready!

Built without sensitive environment variables

Name Link
🔨 Latest commit e92dd52
🔍 Latest deploy log https://app.netlify.com/sites/volview-dev/deploys/6707ff3f45f618000803180a
😎 Deploy Preview https://deploy-preview-611--volview-dev.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@PaulHax PaulHax self-requested a review June 27, 2024 18:27
Copy link
Collaborator

@PaulHax PaulHax left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Works good. Thanks!

@floryst
Copy link
Contributor

floryst commented Jun 27, 2024

This does have an issue where not-yet reconstructed DICOM images aren't included in the cycling. I'm unifying the image list in #606, which should make this easier.

@lchauvin
Copy link
Contributor Author

Has the list of images been unified ?

@PaulHax
Copy link
Collaborator

PaulHax commented Apr 28, 2025

@lchauvin #606 added an imageCacheStore which holds image IDs for DICOM and other image types, even as they are loaded. So the arrow keys probably want to loop through the imageCacheStore.imageIds array.

@floryst
Copy link
Contributor

floryst commented Apr 29, 2025

I've given this some thought, so here are some ideas I had for this feature:

  • the patient studies + images sidebar should have a backing store for it, which defines the order of the seen images. The order of the images in the image cache store might not be particularly useful, since the order still might not be what is visually seen in the sidebar
  • The left/right arrow cycles will use this backing store to select the next image

@PaulHax PaulHax mentioned this pull request May 2, 2025
4 tasks
@lchauvin
Copy link
Contributor Author

lchauvin commented May 7, 2025

Should I wait for the backing store before making any modification ?

@floryst
Copy link
Contributor

floryst commented Aug 19, 2025

Revisiting this PR: we haven't had time to implement this. The idea (if you want to take it on) is to take the logic in ImageDataBrowser + PatientBrowser and move that into a store.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants