Implement undo about material-maker HOT 4 CLOSED

For reference, undo/redo support was implemented in #349.

from material-maker.

If Ctrl + Y isn't used for anything else, it makes sense to support it as a "Redo" shortcut in addition to Ctrl + Shift + Z. There's no real standard here, so supporting both is probably a good idea if possible.

from material-maker.

Undo/Redo will not be easy to implement. I tested a simplistic undo/redo but it was pretty bad performance wise. It's definitely on the roadmap, though... I guess I have a smarter solution, but did not have time to implement it yet.

from material-maker.

Is there a store state system (I might be using the wrong name; please refer to Vue's Vuex) that could be implemented?
In my mind, (as someone who hasn't seen the source code) I think an int for step counts, and an object detailing what was changed in which node; could be enough for an undo-redo.

Pseudo Code;
In this example code, the change is only for moving a node, and changing a value.

{
    "stepsCount": 0,
    "changes": [
        {
            "nodeId": 0,
            "change": {
                "from": {
                    "node_position": { "x": -84.916977,"y": -75.517273 }
                },
                "to": {
                    "node_position": { "x": 1.58463,"y": -75.517273 }
                }
            }
        },
        {
            "nodeId": 0,
            "change": {
                "from": {
                    "parameters": { "scale_y": 1.3 }
                },
                "to": {
                    "parameters": { "scale_y": 1.5 }
                }
            }
        }
    ]
}

Where, for sake of simplicity, Ctrl+(Shift)+Z changes the stepCount, and then the object at changes[change.length-(stepCount+1)] (accessed backwards for simplicity in this example), and thus the change is applied to the node.

Of course, this requires each node to have an id, which shouldn't be a problem, considering they're in order in the nodes array. Of course, if names are preferred, I don't see why it wouldn't be possible.

If keeping it in memory is a problem, I'm not a fan of the idea, but I think maybe accessing it from a file in the app's folder.

Thank you for your time and patience. I hope this could be of use.

from material-maker.