_currentPrintable was set depending on _currentCharCode, which is 112
for both F1 and 'p' keys, fixed after detailed research on which keys
should be considered printable
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.
This fixes tons of warnings with clang from a recent xcode version on
macOS (and possibly other systems) complaining that an instantiation
of _singleton is required but no definition is available.
- DFAF Adventure
- Dreamcat
- Open Quest
Freely available from https://jennibee.itch.io/ these are three (very short) fangames.
All of those games come in three packages (Linux, OSX, Windows32) but all the packages differ only in the platform .exe, the data.dcp stays the same, so the entry is limited to one.
The packages even come with ScummVM 1.8.1
All three games tested and working (didn't solve the Open Quest final riddle though)
One script runtime error encountered in DFAF Adventure on examining the "speaker", other than that fine.
Feel free to give hints on what i should change.
I put scare quotes around "correctly" because I can't swear this is the
intended behaviour of the original interpreter.
I don't think accessing filenames that end with / in the .DCPs is even
defined behaviour, so this is a best guess.
Instead of the engine-based 0, we now default to
kThumbnailWidth/kThumbnailHeight2, as values of 0
here disable thumbnails in the engine.
TODO: Perhaps consider looking into always running the
thumbnail-generation even if the sizes are 0?
Recently we started to use this as new semantics, although in the past
we used simly <engine>_H. Now these guard defines are consistent with
rest of the files which are used in the engines.
lolbot-iichan
Paul Gilbert
Cameron Cawley
David Fioramonti
Bastien Bouclet
Adrian Frühwirth
JenniBee
Colin Snover
Torbjörn Andersson
Eugene Sandulenko
Thierry Crozat
D G Turner
Hubert Maier
Tobia Tesan
Ryper_Zsolt
Einar Johan Trøan Sømåen
Filippos Karapetis