tuckie

So over this weekend I've been writing some more function bindings to test different methods of using node-addon-api with performance in mind. The main challenge performance-wise with this library is...

@DanielMazurkiewicz I'm sorry I didn't see a notification for this one, but hopefully i can clear up some things about how the bindings are written here, and how we deal...

I guess the short of what I'm saying above is that currently: - Almost all instances where a pointer/list are involved it is represented as a JS number _because_ its...

Being able to work directly with arrays would be a benefit in some places, but i don't think it solves all the problems we need to as far as pointers...

Sure. I saw that issue before, but didn't think it was the same issue, but now i see what it means. Would it then be possible to adjust my fonts...

Hey, sorry about the late response - Thanks for the info on this, these seem to be some pretty decent routes to look down. Because it's a pixel font, I...

i believe the functions would just look like this: ```rs unsafe fn buffer_data_null(&self, target: u32, length: isize, usage: u32) { let gl = &self.raw; gl.BufferData( target, length, std::ptr::null() as *const...

SetShaderValue isn't supported because it's not as simple to handle in our C implementation (its a void pointer, but you provide an extra argument to detail what value is supposed...

i remember another solution being that ARM platforms would download both, and then its up to the user to require `raylib` or `raylib/drm`. would something like that help here?

right now the typescript definitions for this are correct - it is a number instead of an array - or rather its a pointer address to the array in c...