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
..
bankman.cpp
bankman.h
command.cpp
command.h
configure.engine
credits.cpp
credits.h
cutaway.cpp
cutaway.h
debug.cpp
debug.h
defs.h
detection.cpp
display.cpp
display.h
graphics.cpp
graphics.h
grid.cpp
grid.h
input.cpp
input.h
journal.cpp
journal.h
logic.cpp
logic.h
midiadlib.cpp
midiadlib.h
module.mk
music.cpp
music.h
musicdata.cpp
POTFILES
queen.cpp	ENGINES: Remove default1x scaler flag	2017-10-07 12:30:29 -05:00
queen.h
resource.cpp
resource.h
restables.cpp
sound.cpp
sound.h
state.cpp
state.h
structs.h
talk.cpp
talk.h
walk.cpp
walk.h
xref.txt