-
Notifications
You must be signed in to change notification settings - Fork 1
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
2D visualizer Z position visualisation -SOW6- #370
Comments
@neuroBazzi we could change the location of the spinal cord figure to the top and make it bigger - might be an easy way to solve this issue |
thanks @syamace-metacell , I agree that making it a little bigger would help, but why does it have to move up? |
@neuroBazzi It's a better position for visibility - referring to the 'Z-shaped pattern' based on user's usual eye movement when looking at an interface. Having said that, with it being the top, it'll likely be one of the first thing a user would see when looking at the tab. |
got it, thank you! |
I like the idea of moving it to the top right. I think that should probably be enough to address their need. (2 hours) |
Thanks @afonsobspinto, is cordmap already outputting all the info you need or do we need @stephenlenzi's help? |
I believe we have everything we need. You can go ahead and fire @stephenlenzi 😛 |
:'( |
From the client:
2D viewer currently shows the z distance from the center in C8 caudal, rather than saying C4 or C6. This may be unintuitive for new users. The current cervical segment is displayed in a small image on the bottom right, which is easy to miss. Ideas for making this more intuitive: have the cervical level displayed ON the 2D plot, or make the spinal cord figure with current location on the bottom right bigger. Or change the text on the 2d plot to “origin in C8 Caudal”?
@stephenlenzi @afonsobspinto is it possible to extract the the cervical level (e.g. C4, C6) and serve it on the FE alongside the distance from C8. Having the distance from C8 was a previous requirement so I would still keep it.
@syamace-metacell could you please look into this?
The text was updated successfully, but these errors were encountered: