Update Magnum submodules with support for querying MeshData size from Python#1878
Update Magnum submodules with support for querying MeshData size from Python#1878
Conversation
|
Nit: on the magnum-bindings. You cast from handle to C++ back to handle with |
|
Hm, but there I need to access |
Ah, I guess in this case it doesn't make quite as much sense. It's very useful for when you are using only python APIs. Also, it would save you a python->C++->python roundtrip, but probably not worth the added complexity here. |
|
Yeah, here it's not that much of a perf bottleneck, so I prefer to have it done the least error-prone way possible. Anyway, thanks for the hints, as always. Much appreciated :) |
Motivation and Context
I was actually false-advertising on the call that it's possible to query
trade.MeshData.index_dataandtrade.MeshData.vertex_datasize from Python. So I added those.For images,
trade.ImageData2D.datawas a thing before already. Those are byte array views, solen()is the byte count.Also contains all other submodule updates that are a part of #1874 as well. Nothing controversial or attention-worthy there, since all those changes are mostly just related to glTF export that only the batch renderer uses.
How Has This Been Tested
My CIs pass.