binding

Some users have specific use cases where they would benefit from being able to access the PYO3_CONFIG_FILE values in some form from the pyo3 crate.

I generally wouldn't advise this, as a lot of these config files (such as library path) are unique to the build environment so wouldn't have any useful meaning in binaries intended to be deployed on other systems.

See original comment from #2

Create an example that debounces events fired:
Use a range input to define the debouncing-interval and offer a button that uses this interval debouncing it's clicks.

Discussion on the state of documentation for this library.

Code comments.

Using the same comments with the same style as raylib. One idea is to change them to the xmldoc style which can be used to generate external documentation. Unsure if this should be done but worth looking into.

Tech notes

Documenting api differences to make it easier for people new to raylib. Could move deta