-
Notifications
You must be signed in to change notification settings - Fork 38
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
Improvements to ROI presentation and UI support #184
Comments
Additional ideas related to visualization of the individual regions:
|
Related suggestions from Javed Khan group communicated by @curtislisle:
|
Feedback from Tom G:
|
@pedrokohler I tested in the IDC test tier, and I do not understand why the color of the large annotation in the top part of the image changes color when I select regions for the annotations in the bottom part. I do not understand the logic for highlighting that is implemented right now, it is not intuitive. I suggest we have a quick meeting sometime next week to discuss this. |
Thank you for looking into multiple colors for different annotation types. This will be popular with our scientists. On Nov 1, 2024, at 5:29 PM, Andrey Fedorov ***@***.***> wrote:
@pedrokohler I tested in the IDC test tier, and I do not understand why the color of the large annotation in the top part of the image changes color when I select regions for the annotations in the bottom part. I do not understand the logic for highlighting that is implemented right now, it is not intuitive. I suggest we have a quick meeting sometime next week to discuss this.
2024-11-01_17-24-52.1.gif (view on web)
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Can you provide the URL? |
Right now, on this example, same color is applied, and it is impossible for the user to tell different kinds of ROI one from another
https://andrey-slim-test.web.app/studies/2.25.155017484756498730492136597238994838876/series/1.3.6.1.4.1.5962.99.1.3434988325.342625608.1687062201125.4.0
The text was updated successfully, but these errors were encountered: