-
-
Notifications
You must be signed in to change notification settings - Fork 38
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
Update to wgpu-native v0.18.1.1 #429
Conversation
As for #352, it looks like the warnings (when dragging a window from one monitor to another on Windows+Qt) cannot be avoided without breaking window resizing on other systems. Nevertheless, the window is not in a broken state anymore where a resize is needed to get it working again. In other words, the error messages are annoying but otherwise harmless. |
almost done now 😅 |
The reason why I want this is that the latter is a native-only feature (not part of the webgpu spec). This means that using it also unlocks other stuff, and accidentally using that may cause downstream code to become incompatible with WebGPU. I tried adding it to wgpu-native (gfx-rs/wgpu-native#322), but the feature is simply not implemented in wgpu-core yet. I'm looking into adding it there, but it will take some time before that lands in a new wgpu-native release. |
Fixed the pypy memytest with another well-placed |
closes #352
CanvasContext
's don't clean up properly.Some calls can pass null pointer, checkthat nullable texture only applied to that particular situation, and we've got that covered.WGPU_NULLABLE
and check for it.Float32Filterable
rather thanWGPUNativeFeature_TextureAdapterSpecificFormatFeatures
-> not yetAfter this is merged: