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
..
anim.cpp
anim.h
configure.engine
console.cpp
console.h
detection.cpp
dispman.cpp
dispman.h
engine.cpp
eventman.cpp
eventman.h
image.cpp
image.h
interface.cpp
interface.h
intro.cpp
intro.h
lab.cpp
lab.h
labsets.cpp
labsets.h
map.cpp
module.mk
music.cpp
music.h
processroom.cpp
processroom.h
resource.cpp
resource.h
savegame.cpp
special.cpp
speciallocks.cpp
speciallocks.h
utils.cpp
utils.h