-
Notifications
You must be signed in to change notification settings - Fork 74
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
Cubeviz should have coordinates display like Imviz #1090
Comments
This issue is tracked on JIRA as JDAT-1960. |
Comment by Pey-Lian Lim on JIRA: Are you concerned only with the 2D sliced WCS or you want also the 3D WCS shown? Is there a mock up? You also have to hook this up to the cube slider and make sure when someone slides too fast, it doesn't try to update constantly. |
Comment by Kyle Conroy on JIRA: JDAT-1430 asks for similar but for specviz. These would probably be easiest to do in a single effort (generalizing the current imviz implementation for all viewers/viztools) |
Comment by Richard O'Steen on JIRA: Could subclass the Cubeviz viewers off of the Imviz one, or could ducktype it. Goal is this feature, ok if we're not totally pulling in the Imviz viewer now. |
Comment by Pey-Lian Lim on JIRA: Re: specviz -- I would say that is separate work because the info being shown will be different and needs some UI consideration that is different from images. |
Comment by Pey-Lian Lim on JIRA: See #1315 |
Reporter: pllim
As a user, I want to see the information under my cursor when I mouseover the datacube display. Unlike Imviz, the plugin needs to be aware which 3D slice is currently shown (Imviz understand the concept of each 2D image as a glue data layer, but Cubeviz is a different beast).
Can probably copy a lot of stuff from the Imviz implementation, but not all of them. Actually, maybe might be able to use the same plugin but the viewer hook-up would be different.
🐱 👻
DISCLAIMER: This issue was autocreated by the Jdaviz Issue Creation Bot on behalf of the reporter. If any information is incorrect, please contact Duy Nguyen
The text was updated successfully, but these errors were encountered: