You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the docs list enums, but they don’t actually exist as objects - cffi just converts all the values to ints.
So first we need to fix the docs.
Then, is there an automated way we could make real enums? Or just put the ints into appropriate namespaces so they are grouped appropriately together in the docs?
separating raygui etc into a different namespace would also be nice, but I’m not sure how since the original C puts all the functions into the same global namespace.
The text was updated successfully, but these errors were encountered:
Python has the Enum module which may be useful? Exec is usually discouraged but in certain scenarios it's fine, as this isn't running untrusted code. And recently Raylib released an official way to make automated bindings which could potentially help? If using the automated bindings, using SimpleNamespace could also help you collect the modules together
…ay itself for backwards compability) add proper enums to pyray and to pyray hints/docs (generated from raylib.json). TODO: raygui, rlgl, maybe something for the C API. See issue #52
Currently the docs list enums, but they don’t actually exist as objects - cffi just converts all the values to ints.
So first we need to fix the docs.
Then, is there an automated way we could make real enums? Or just put the ints into appropriate namespaces so they are grouped appropriately together in the docs?
The text was updated successfully, but these errors were encountered: