Alexander Hinze
Alexander Hinze
> Hey, apologies for the delays here - it's a period of multiple vacations as well as parental leaves, which has left the Kotlin team very understaffed. We expect folks...
Yes, something else **is** definitly going on outside the API and my code. It seems to be a general issue on my system where i'm not able to capture any...
> @KitsuneAlex I had mixing Vulkan and OpenGL initialization, which leads to no capture in renderdoc. How would i identify such issue?
At least for Kotlin/Native, i have [a good implementation](https://git.karmakrafts.dev/kk/multiplatform-mman/-/blob/master/multiplatform-mman/src/nativeMain/kotlin/io/karma/mman/MemoryRegion.kt?ref_type=heads#L121-128) that's based on kotlinx.io as a possible starting point. You could easily adapt this to Kotlin/JVM too.
> @thatcosmonaut the pr does not change the behavior. Can confirm, issue is persisting for me on PopOS 22.04/Kernel 6.9.3-76060903-generic/X11/NVIDIA 560.35.03
Hey there ^^ I don't see why this would be needed, i intentionally left out all functionality that isn't strictly required to use this library. You can invert the y-axis...
Giving this a bump since this is a major holdback for our company at the moment.
An easy workaround for this issue for the time being is adding some inline code to your lexer grammar that conditionally pops the mode stack. For Java this may look...
Gonna fix the last remaining issues with this later today hopefully :)