-
Notifications
You must be signed in to change notification settings - Fork 372
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 primitives ordering/layering #1988
Comments
Let's avoid confusion by not calling this "Z". A depth-image contains Z-values, but can also have a draw-order/layer which is completely unrelated. |
We should consider using defaults, like https://matplotlib.org/3.1.1/gallery/misc/zorder_demo.html does: eg:
|
Proposal: Max one |
We should also have a default
I don't think wee need to do this for the first version, but keep it in mind. |
Implementation:For 2D viewsSimple way:Paint 2D stuff first, using the Does not support showing 2D stuff on top of 3D stuff, but that's ok for now. More complex way:Paint 3D stuff to a texture. The ID buffer complicates this. For 2D planes in 3D viewsTake the all the Take these integers as the |
We don't currently define which order 2D shapes are painted. Once we support more primitives like filled rectangles, circles, text etc, it will be very important to be able to specify what is on top of what.
We also need good default, e.g. images should probably be furthest down whatever happens.
We should maybe default to painters-algorithm (whatever is logged first is painted furthest back), as that is what many users are used to from e.g. opencv.
Let's investigate nomenclature other libraries and tools use.
The text was updated successfully, but these errors were encountered: