Age | Commit message (Collapse) | Author | |
---|---|---|---|
2018-06-30 | ENGINES: Add missing dependencies for several engines | Cameron Cawley | |
2018-05-24 | JANITORIAL: Fix trailing whitespace | Adrian Frühwirth | |
2018-05-01 | PLUMBERS: Push down the AD includes | Bastien Bouclet | |
2018-04-07 | PLUMBERS: Optimized heap allocation | whitertandrek | |
No sense in deleting and then allocating an object again because loadStream method destroy previous data. | |||
2018-04-07 | PLUMBERS: Removed unnecessary calls | whitertandrek | |
destructor of Common::File anyway calls close method | |||
2018-04-07 | PLUMBERS: Change file allocation from heap to stack | whitertandrek | |
2018-04-07 | PLUMBERS: Remove unnecessary conditional | whitertandrek | |
delete perfoms the check anyway | |||
2018-03-26 | PLUMBERS: Remove unused parameter | Eugene Sandulenko | |
2017-11-26 | PLUMBERS: Remove unstable flag and enable by default | Thierry Crozat | |
2017-10-07 | ENGINES: Remove default1x scaler flag | Colin 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-31 | PLUMBERS: Initialize some variables | Strangerke | |
2017-05-03 | PLUMBERS: Add engine for Plumbers Don't Wear Ties | Retro-Junk | |