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
Is your feature request related to a problem? (optional)
No response
Description of the new feature/enhancement
For our ophthalmology PACS it would be much more convenient if the thumbnail of a study is based on the first image in the series. We even have series in which the first image is especially built to show information about the study in the thumbnail. I understand that Weasis takes by default the center image of a series to build the thumbnail. The thumbnail can be rebuild based on a different image (first, last), but it does not seem possible to use the first image by default. Could this be implemented in the preferences in a future version? Or is there a workaround for this?
For the moment, there is no such preference by default.
This preference could be added, but I think we have to associate SOP Class UIDs with this preference, otherwise you won't get the desired effect if you look at several types of imaging.
Thanks Nicolas. Indeed associating it with the SOP Class UID would give the most flexibility, but is also more work. For us, it would be really helpful already, if for all SOP classes the first image can be taken for the thumbnail.
Is your feature request related to a problem? (optional)
No response
Description of the new feature/enhancement
For our ophthalmology PACS it would be much more convenient if the thumbnail of a study is based on the first image in the series. We even have series in which the first image is especially built to show information about the study in the thumbnail. I understand that Weasis takes by default the center image of a series to build the thumbnail. The thumbnail can be rebuild based on a different image (first, last), but it does not seem possible to use the first image by default. Could this be implemented in the preferences in a future version? Or is there a workaround for this?
Thanks for a great tool!
Proposed technical implementation details (optional)
No response
Describe alternatives you've considered (optional)
No response
Additional context (optional)
No response
The text was updated successfully, but these errors were encountered: