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
..
modules
background.cpp
background.h
blbarchive.cpp
blbarchive.h
configure.engine
console.cpp
console.h
detection.cpp
diskplayerscene.cpp
diskplayerscene.h
entity.cpp
entity.h
gamemodule.cpp
gamemodule.h
gamevars.cpp
gamevars.h
graphics.cpp
graphics.h
klaymen.cpp
klaymen.h
menumodule.cpp
menumodule.h
messages.h
microtiles.cpp
microtiles.h
module.cpp
module.h
module.mk
mouse.cpp
mouse.h
navigationscene.cpp
navigationscene.h
neverhood.cpp
neverhood.h
palette.cpp
palette.h
POTFILES
resource.cpp
resource.h
resourceman.cpp
resourceman.h
saveload.cpp
scene.cpp
scene.h
screen.cpp
screen.h
smackerplayer.cpp
smackerplayer.h
smackerscene.cpp
smackerscene.h
sound.cpp
sound.h
sprite.cpp
sprite.h
staticdata.cpp
staticdata.h