Skip to content
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

Selecting a point (instance) and selecting a pixel is conceptually different when it shouldn't #853

Open
Wumpf opened this issue Jan 20, 2023 · 1 comment
Labels
📺 re_viewer affects re_viewer itself

Comments

@Wumpf
Copy link
Member

Wumpf commented Jan 20, 2023

Today images are logged as blobs and points as list of components. But as a user this distinction isn't all that meaningful, especially from Python where in both cases one logs numpy arrays.

Hovering & selecting an image:
image
-> We clearly hover a pixel, but select the whole image

Hovering & selecting a point:
image
-> We clearly hover a point and select a point. However, we don't get to see any information of the object to which the user logged all these points.

UI wise we'd like to have "both in both cases": We want to get information about the object holding the data (in one case the image, in the other the point cloud object) but also want to be aware of the fact that we selected a single pixel and a single point!

@Wumpf Wumpf added the 📺 re_viewer affects re_viewer itself label Jan 20, 2023
@Wumpf
Copy link
Member Author

Wumpf commented Apr 11, 2023

we decided that internally pixels will be identified via instance ids. That implies that images conceptually a collection of pixel instances together with some meta data! See #1756

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
📺 re_viewer affects re_viewer itself
Projects
None yet
Development

No branches or pull requests

1 participant