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
..
configure.engine
console.cpp
console.h
detection.cpp
dialogs.cpp
dialogs.h
display.cpp
display.h
file_v1d.cpp
file_v1w.cpp
file_v2d.cpp
file_v2w.cpp
file_v3d.cpp
file.cpp
file.h
game.h
hugo.cpp	ENGINES: Remove default1x scaler flag	2017-10-07 12:30:29 -05:00
hugo.h
intro.cpp
intro.h
inventory.cpp
inventory.h
module.mk
mouse.cpp
mouse.h
object_v1d.cpp
object_v1w.cpp
object_v2d.cpp
object_v3d.cpp
object.cpp
object.h
parser_v1d.cpp
parser_v1w.cpp
parser_v2d.cpp
parser_v3d.cpp
parser.cpp
parser.h
POTFILES
route.cpp
route.h
schedule.cpp	JANITORIAL: Silence more GCC 7 warnings	2017-08-06 13:30:51 +02:00
schedule.h
sound.cpp
sound.h
text.cpp
text.h
util.cpp
util.h