Chris Dill
Chris Dill
@9ParsonsB A point-release for this fix sounds like a good idea. @graphnode Thanks for the fix. Merged!
There is a unsafe version of `LoadImageFromMemory` you can use. I will consider adding utils for other LoadXFromMemory functions.
We decided to split the safe utils from the unsafe bindings to make it more flexible and easier to debug. Performance depends on your use case.
`LoadCodepoints` returns 8595 for ↓ and 8593 for ↑. So these would not be included by default loading up to 5000. Changing to a number higher than this and I...
You can also use `LoadFontEx` and pass in just the codepoints you want. I made a few fixes when testing this that will be in the next release.
Currently the bindings are not ideal in places like this. See [this issue] (https://github.com/ChrisDill/Raylib-cs/issues/9) for details. You can Marshal the data or use Span around it. I tried Span before...
No worries. I'm glad you found the bindings useful! I want to improve it at some point. I have seen some improvements in 2.6-dev that should help like changing the...
@StevenGann Any updates on this issue? In the end I decided to drop the idea of wrapping IntPtr variables internally because there are different ways to access/modify them. That said,...
@Crydsch The data for the mesh is public so you can make custom wrappers if needed. I might add some functions for creating Span types but I need to experiment...
It might be possible to convert it to a raylib Image by creating it directly. You need to check the pixel format matches and make sure the data is unmanaged....