I've been doing a fairly common implementation of event
handling across multiple engines, so this is an attempt
to generalize it. Eventually I'd like to see it moved
out of Chewy entirely, and be available for use in other
engines.
This flag is removed for a few reasons:
* Engines universally set this flag to true for widths > 320,
which made it redundant everywhere;
* This flag functioned primarily as a "force 1x scaler" flag,
since its behaviour was almost completely undocumented and users
would need to figure out that they'd need an explicit non-default
scaler set to get a scaler to operate at widths > 320;
* (Most importantly) engines should not be in the business of
deciding how the backend may choose to render its virtual screen.
The choice of rendering behaviour belongs to the user, and the
backend, in that order.
A nearby future commit restores the default1x scaler behaviour in
the SDL backend code for the moment, but in the future it is my
hope that there will be a better configuration UI to allow users
to specify how they want scaling to work for high resolutions.
Various engine variables are passed down to sub-objects, but never used
currently causing compiler warnings. It is unclear if these are intended
to be used in future, but have removed for now, rather than commenting
out as that would be messier. Can be restored easily if necessary in
future.
Currently, speech and sound effects are supported, but the current
music playing implementation is wrong, as the game's music is
encoded in custom MOD-like files. With the current music
implementation, the PCM parts of these files are played
