NOTE: A working keyboard must be attached to the Raspberry Pi while testing this, otherwise it's impossible to actually quit the emulator.
raylib takes possession of the SSH keyboard for some reason, which makes it so you can't Ctrl+C out of the emulator over SSH, you must Ctrl+C or press Q on the Pi keyboard.
A mostly working RTG implementation using raylib instead of SDL2.0
Greatly decreases the rendering overhead for 8bpp modes and gets rid of the need for hardware ARGB888 texture format support.
RTG will be initialized using the resolution of the Raspberry Pi, and onbly the 320x200/320x240 modes are currently scaled to the full vertical area of the screen.
* Buttons and boxes height reduced
* Almost everything moved around a bit to make space
* Added shutdown button
* Added kickstart switch gadgets
* Switched from AutoRequest to rtEZRequest for most things (apart from
the error where we couldn't load reqtools)
* Text fixes
GUI version 0.2 alpha.
You can now retrieve a file from PiStorm to save in your Amiga. Reqtools
now included to pick a destination drive / directory.
Also a reboot button was added and some other things fixed.
It can only change the config file and enable/disable RTG right now, but
it a framework for adding more things in the future.
Some of the CLI tool code was slightly modified for VBCC compatibility,
most importantly, some macros that didn't work were expanded and some
includes were changed.
Ported over my ROM identification code, mostly to identify when you are
using a ROM that won't boot and log it. But also cool to log which ROM
is booting if we need to help a user.
Managed to forget to stage one line of code for the last commit...
Also fixes the Z3 Autoconf memory range staying active after being configured, prevents some rare memory wraparounds.
Mapped memory ranges should always be given preference, since they can't actually cause a bus error or affect any read/write operations over the 68k bus.
please note that if loopcycles = 0 then the emulation thread may never
notice the quit request. needs replacing with some form of thread signal
eventually, but that will require a signal handler.
this change uses an ioctl to disconnect the keyboard event device from
the input layer, meaning input no longer affects the pi and will
entirely be consumed by the pistorm emulator process.
