aboutsummaryrefslogtreecommitdiff
path: root/engines/plumbers
AgeCommit message (Collapse)Author
2018-06-30ENGINES: Add missing dependencies for several enginesCameron Cawley
2018-05-24JANITORIAL: Fix trailing whitespaceAdrian Frühwirth
2018-05-01PLUMBERS: Push down the AD includesBastien Bouclet
2018-04-07PLUMBERS: Optimized heap allocationwhitertandrek
No sense in deleting and then allocating an object again because loadStream method destroy previous data.
2018-04-07PLUMBERS: Removed unnecessary callswhitertandrek
destructor of Common::File anyway calls close method
2018-04-07PLUMBERS: Change file allocation from heap to stackwhitertandrek
2018-04-07PLUMBERS: Remove unnecessary conditionalwhitertandrek
delete perfoms the check anyway
2018-03-26PLUMBERS: Remove unused parameterEugene Sandulenko
2017-11-26PLUMBERS: Remove unstable flag and enable by defaultThierry Crozat
2017-10-07ENGINES: Remove default1x scaler flagColin Snover
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-05-31PLUMBERS: Initialize some variablesStrangerke
2017-05-03PLUMBERS: Add engine for Plumbers Don't Wear TiesRetro-Junk