Almar Klein

We don have not really defined what info should be in the pick info, but we try to give enough info so the user can reconstruct with reasonable accuracy where...

> basically a collection of functions IO is inherently messy. By constraining it to a specific namespace, it's somewhat scalable without affecting the main pygfx API.

We've covered most things mentioned above by now. The GUI stuff is developed in Rendercanvas, and continuously improving. Some points that remain: * The async stuff needs a bit of...

LGTM. Anyone know what the deal is with `WGPUAdapterProperties` vs `WGPUAdapterInfo`?

> I'm not sure how wgpu-native decides which version of wgpu to use. Here's an example: https://github.com/gfx-rs/wgpu-native/pull/402 Basically bumping versions in `cargo.toml` and then making the necessary changes. It usually...

That's correct. The latest tag from wgpu-core is 22.1.0. The versioning of wgpu-native is to take the version of wgpu-core and add a fourth number to it. We've had a...

The work has started some time ago: https://github.com/gfx-rs/wgpu-native/pull/441

_Original comment by_ **lansman (Bitbucket: [lansman](http://bitbucket.org/lansman), GitHub: [lansman](http://github.com/lansman))**: --- Code is displayed incorrectly. You can see the correct code [on PEP08 page](http://www.python.org/dev/peps/pep-0008/) in section "Indentation".

I decided to put effort into finishing #873, because it contains some changes to support multi-layer textures. So option B is easier to implement. Having thought about this some more,...

Option B: multi-layer textures can still be useful, but let's open a new issue when that becomes relevant.