Colin Snover 432fd522d2 ENGINES: Remove default1x scaler flag ... 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.		2017-10-07 12:30:29 -05:00
..
adlib.cpp
balloons.cpp
callables_br.cpp
callables_ns.cpp
configure.engine
debug.cpp
debug.h
detection.cpp
dialogue.cpp
disk_br.cpp
disk_ns.cpp
disk.h
exec_br.cpp
exec_ns.cpp
exec.cpp
exec.h
font.cpp
gfxbase.cpp
graphics.cpp
graphics.h
gui_br.cpp
gui_ns.cpp
gui.cpp
gui.h
input.cpp
input.h
inventory.cpp
inventory.h
module.mk
objects.cpp
objects.h
parallaction_br.cpp
parallaction_ns.cpp
parallaction.cpp
parallaction.h
parser_br.cpp
parser_ns.cpp
parser.cpp
parser.h
POTFILES
saveload.cpp
saveload.h
sound_br.cpp
sound_ns.cpp
sound.h
staticres.cpp
walk.cpp
walk.h