ForeverZer0

Will definitely take a look at the templates, really like that idea. My Python-foo is a bit lacking as I rarely use it, but I am sure I could stumble...

Looking at this right now, perhaps I am missing something, but I do not even see why I chose to call `base.Close()` or what purpose it is even serving, other...

I am very likely going to target .NET Core with the next release to take advantage of dynamically finding the library, which uses different naming conventions on different operating systems....

The .a files are static libraries versions glfw, typically for embedding into a C application, you do not need those, only the shared (.dll) one. Assuming that you have those...

I think I can get an updated release pushed out within the next few days, I have admittedly been a little complacent with this project lately working on a small...

This will likely be added with the next update of the upstream. Currently, GLFW does not have an event driven callback for joysticks, which means the user has to manually...

The upstream GLFW project has not yet implemented it unfortunately. They have recently done some work with enabling/disabling joystick input with init hints, which is likely an important precursor to...

AFAIK, the DLL map is framework dependent, and the way that Mono handles resolving native libraries. .NET Core uses `AssemblyLoadContext`, as well as there are cross-framework implementations like [NativeLibraryLoader](https://github.com/mellinoe/nativelibraryloader). For...

Closing this for now. Will likely revisit the idea with the official release of .NET Core 3.0, and the new features that will be including for native library resolving (the...

@Rjvs Good call, will do. Work on this has been agonizingly slow, just life happening, but will be done in the foreseeable future.