* MacOSX with input events and mfb_set_viewport
* Windows with input events and mfb_set_viewport
* Minor changes in macosx and windows
* X11 with input and mfb_set_viewport
* Minor changes on X11
* Fix bug in X11 resize event
* Fix bug in windows resize
* added scale image to X11
* Added stretch_image with & without bilinear interpolation
* moved MiniFB_internal.h
* Added wayland events
* minor changes
* unify a bit the window structs
* More work on wayland
* Added cmake file
* minor fix on windows
* modified test
* Fix on wayland.
Unset wayland as default for linux
* Use stdbool instead of our own macro eBool
Remove prefix e from all enums
* Remove _ex sufix in common files
* merge X11MiniFB_ex.c into X11MiniFB.c
* Merge WaylandMiniFB_ex.c into WaylandMiniFB.c
* Add user_data to callbacks
* Merge WinMiniFB_ex.c into WinMiniFB.c
* Some minor changes on Windows
* Fix bug on Wayland
* Added mfb_get_key_name
* keyboard_default on all platforms
It wasn't detecting that the window was closed when I closed it by
clicking the red X button. As a result, the window would close, but
mfb_update() didn't return -1, so the program kept running.
This was fixed by listening to the willClose event and using it to set a
flag. I'm not sure if this is the best way to do it, I really know
nothing about OSX/Cocoa.
Also, I fixed a few unused varible warnings. And warnings related to
NSUInteger not matching the expected signature with NSWindowStyleMask.
* x11: need to return somethin from processEvents()
* Added wayland support
* Documented how to use wayland support
* wayland: re-attach the buffer to actually trigger an update
* wayland: use the seat_listener
bmiColors is a C style flexible array with a default value of 1, so the bmiColors[1] and bmiColors[2] were accessing memory out of bounds and causing very weird stuff to happen. Fixed by doing the appropriate flexible buffer allocation.
