Age | Commit message (Collapse) | Author | |
---|---|---|---|
2017-11-18 | FULLPIPE: Fix memory leaks of PreloadItems | Colin Snover | |
2017-11-18 | FULLPIPE: Remove manual memory management of use list | Colin Snover | |
2017-11-18 | FULLPIPE: Fix memory leaks of InventoryPoolItem | Colin Snover | |
2017-11-18 | FULLPIPE: Fix leaks of DynamicPhases | Colin Snover | |
I am not entirely sure this is a correct fix for these leaks; there is still the issue of the last member of _dynamicPhases being invalidated and not removed sometime before the destruction of Movement. Also, some of the items in this array are not actually owned by Movement so deleting them will cause double-frees or use-after-frees. It may be the case that a second list should be maintained instead containing only the objects that are created internally within Movement. Further testing will tell for sure. | |||
2017-11-18 | FULLPIPE: Fix memory leaks of MctlItems in MctlCompound | Colin Snover | |
2017-11-18 | FULLPIPE: Clarify ownership of DynamicPhase::_exCommand | Colin Snover | |
2017-11-18 | FULLPIPE: Clarify ownership of pointer arrays in StaticANIObject | Colin Snover | |
2017-11-18 | FULLPIPE: Fix memory leaks in PictureObject, Background | Colin Snover | |
2017-11-18 | FULLPIPE: Use flag enum | Colin Snover | |
2017-11-18 | FULLPIPE: Fix memory leak of graph nodes and lists | Colin Snover | |
2017-11-18 | FULLPIPE: Remove unnecessary constructors | Colin Snover | |
These appear to be default member-wise copy constructors or POD constructors that zero all members. I suspect that quite a few pointer-taking constructors are actually supposed to be copy-constructors but since they don't all just do default member-wise copies I do not feel confident in changing them without verifying that there are not separate copy constructors in the disassembly, and I don't have the database for this game. | |||
2017-11-18 | FULLPIPE: Fix memory leaks, ownership issues with various point lists | Colin Snover | |
2017-11-18 | FULLPIPE: Disable some unused code paths | Colin Snover | |
2017-11-18 | FULLPIPE: Annotate ownership rule of MfcArchive::readClass | Colin Snover | |
2017-11-18 | FULLPIPE: Fix memory leaks and unnecessary indirect allocations in Motion ↵ | Colin Snover | |
and Sc2 | |||
2017-11-18 | FULLPIPE: Fix memory leak of global message queues | Colin Snover | |
2017-11-18 | FULLPIPE: Fix memory leaks in ModalMainMenu | Colin Snover | |
2017-11-18 | FULLPIPE: Remove unnecessary and unsafe C-style casts | Colin Snover | |
2017-11-18 | FULLPIPE: Fix deleted queue leaks & clarify flags | Colin Snover | |
2017-11-18 | FULLPIPE: Reduce chance of Scene leaks, remove unused SceneTag member | Colin Snover | |
2017-11-18 | FULLPIPE: Remove unused gap data from EntranceInfo | Colin Snover | |
2017-11-18 | FULLPIPE: Fix memory leaks and ownership problems with Behavior objects | Colin Snover | |
2017-11-18 | FULLPIPE: Correctly fix Bitmap leaks | Colin Snover | |
2017-11-18 | FULLPIPE: Fix memory leak of MGMItem | Colin Snover | |
2017-11-18 | FULLPIPE: Fix memory leaks of MovTable and remove unnecessary extra class | Colin Snover | |
2017-11-18 | FULLPIPE: Remove manual memory management of streams | Colin Snover | |
2017-11-18 | FULLPIPE: Use bool literals instead of ints for bool properties | Colin Snover | |
2017-11-18 | FULLPIPE: Take references instead of pointers for required arguments in ↵ | Colin Snover | |
statics, remove unnecessary Picture allocation | |||
2017-11-18 | FULLPIPE: Remove memory leaks and manual memory management in Scene | Colin Snover | |
2017-11-18 | FULLPIPE: Fix memory leaks of SceneTag | Colin Snover | |
2017-11-18 | FULLPIPE: Remove unnecessary and illegal C-style casts | Colin Snover | |
2017-11-18 | FULLPIPE: Fix memory leak of save game thumbnail | Colin Snover | |
2017-11-18 | FULLPIPE: Fix leaks and unnecessary extra allocations in FullpipeEngine | Colin Snover | |
2017-11-18 | FULLPIPE: Fix memory leak & unnecessary heap allocation of Rects | Colin Snover | |
2017-11-18 | FULLPIPE: Fix memory leaks of inventory icons and items | Colin Snover | |
2017-11-18 | FULLPIPE: Fix memory leaks in ModalVideoPlayer | Colin Snover | |
2017-11-18 | FULLPIPE: Handle quit/RTL events correctly | Colin Snover | |
Fixes Trac#10316. | |||
2017-11-18 | FULLPIPE: Remove unnecessary extra allocation for RNG | Colin Snover | |
2017-11-18 | FULLPIPE: Fix leaks of MGMSubItem | Colin Snover | |
2017-11-18 | FULLPIPE: Improve memory ownership in Motion | Colin Snover | |
2017-11-18 | FULLPIPE: Make TODO labelled so it is picked up by tools | Colin Snover | |
2017-11-18 | FULLPIPE: Fix memory leaks, ownership issues, and endianness issues in ↵ | Colin Snover | |
graphics code | |||
2017-11-18 | FULLPIPE: Fix whitespace errors | Colin Snover | |
2017-11-18 | FULLPIPE: Make dimensions/coordinate getters pure functions | Colin Snover | |
2017-11-18 | FULLPIPE: Remove illegal C-style cast to incompatible type | Colin Snover | |
2017-11-18 | FULLPIPE: Improve memory safety and fix leaks in sound code | Colin Snover | |
2017-11-18 | FULLPIPE: Improve memory safety and typing of NGIArchive | Colin Snover | |
2017-11-18 | FULLPIPE: Fix illegal C-style cast to incompatible type | Colin Snover | |
2017-10-25 | Merge pull request #1035 from bgK/require-64bits-integers | Bastien Bouclet | |
BUILD: Require 64bits integers | |||
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. |