Hi @gen2brain!
I'm working on raygui's bindings for WASM and I've found that some of the bindings here are not implementing raygui.h correctly.
For example, ToggleSlider returns the active, but raygui.h returns 0 or 1, marking whether the component is pressed or not. There are some functions such as Spinner that implement raygui's behavior correctly, and return a boolean as it is intended.
What I propose is to do some changes to the raygui bindings so they are more consistent with raygui.h, like passing an *int32 instead of an int32 for arguments such as active.
I'm glad to do the fixes myself, but as this is an API breaking change, I'd rather wait until I get your opinion on this issue.
Hi @gen2brain!
I'm working on raygui's bindings for WASM and I've found that some of the bindings here are not implementing
raygui.hcorrectly.For example,
ToggleSliderreturns theactive, butraygui.hreturns0 or 1, marking whether the component is pressed or not. There are some functions such asSpinnerthat implementraygui's behavior correctly, and return a boolean as it is intended.What I propose is to do some changes to the
rayguibindings so they are more consistent withraygui.h, like passing an*int32instead of anint32for arguments such asactive.I'm glad to do the fixes myself, but as this is an API breaking change, I'd rather wait until I get your opinion on this issue.