Analyse code that manipulates the map editor

[azurda]

From reading the code and some tests we have two options both of them doable:

1. Leverage the usage of DO_StoreUndo to generate snapshots of WDFUSE's memory objects instead of the current manual snapshot: Requires code analysis of when to perform this calls so every map function should store a snapshot, minimal code changes probably aside from a list of objects storing all the snapshots.
2. Create a procedure that handles events and undos the latest event based on insertion/deletion/move/change: Requires code analysis and extra implementation, may be worth for REDO because it would save half the work.

I think the best idea is to do 1., the same way the UNDO is leveraged could be used to apply snaphots of undone events, after implementing this we could observe how limited this is and build features on top.

[azurda]

List of functions that create or modify elements:

function  MakeAdjoin(sc, wl : Integer) : Boolean;
function  MakeLayerAdjoin(sc, wl : Integer) : Boolean;
function  UnAdjoin(sc, wl : Integer) : Boolean;
function  MultiMakeAdjoin : Integer;
function  MultiUnAdjoin : Integer;

procedure ShellInsertSC(cursX, cursZ : Real);
function  DeleteSC(sc : Integer) : Boolean;
procedure MultiDeleteSC;
procedure ShellDeleteSC;

procedure ShellInsertOB(cursX, cursZ : Real);
function  DeleteOB(ob : Integer) : Boolean;
procedure MultiDeleteOB;
procedure ShellDeleteOB;

procedure ShellExtrudeWL(sc, wl : Integer);
procedure ShellSplitWL(sc, wl : Integer);
procedure SplitWL(sc, wl : Integer);
function  ShellDeleteWL(sc, wl : Integer) : Boolean;

procedure ShellSplitVX(sc, vx : Integer);
procedure ShellDeleteVX(sc, vx : Integer);