Andre Weissflog

...ok, let's continue the discussion in the PR: https://github.com/floooh/sokol/pull/1048 :) I found a fix for the `sfetch_callback_t` problem => detailed in the PR comment.

Ok, last remaining steps in this comment: https://github.com/floooh/sokol/pull/1048#issuecomment-2113012476

Doh I overlooked something :D The module is currently called sfetch.zig, but it should be called fetch.zig (and imported as `sokol.fetch`) to be consistent with the other modules. Let me...

sokol and sokol-zig also fixed, looking at the pr now

Ok, that's it, thanks! If you notice any problems when actually using the bindings let me know and we can figure out the solution (I'll write a reminder ticket to...

Hopping in here because I just ran against the viewport size restriction: - Metal definitely allows the viewport rectangle to clip the screen boundaries, only the scissor rectangle must be...

PS: > Limiting viewports to -2..2 like Vulkan would not really improve ergonomics I don't agree, this is 2x the maximum supported texture size to each side, this would definitely...

To quote the relevant parts from the Vulkan documentation (https://registry.khronos.org/vulkan/specs/1.3-extensions/man/html/VkPhysicalDeviceLimits.html) * viewportBoundsRange[2] is the [minimum, maximum] range that the corners of a viewport must be contained in. This range must...

PS afterthought: naturally, the role of GPUFences should be considered too... As far as I understand it, fences can be used to prevent the application code from running too far...

@kvark yeah, I'm mainly concerned about the upper bound for memory consumption, e.g. 2x vs 3x is ok, but it shouldn't be allowed to be higher. There might also be...