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
..
actor.cpp
actor.h
animation.cpp
animation.h
callbacks.cpp
configure.engine
console.cpp
console.h
detection.cpp
dialog.cpp
dialog.h
font.cpp
font.h
inventory.cpp
inventory.h
module.mk
music.cpp
music.h
objects.cpp
objects.h
pack.cpp
pack.h
POTFILES
resources.cpp	ALL: Leave out instructions for engine data issues	2016-12-08 13:38:56 +01:00
resources.h
scene.cpp	TEENAGENT: Fix fall through case statements	2017-08-11 21:30:13 +02:00
scene.h
segment.cpp
segment.h
surface_list.cpp
surface_list.h
surface.cpp
surface.h
teenagent.cpp	ENGINES: Remove default1x scaler flag	2017-10-07 12:30:29 -05:00
teenagent.h