making an editor for something and trying to figure out how to implement undo/redo, in the past I would just save the file to memory after every change and store it in a stack, but this editor the files are gonna be tens of megabytes in size
I don't know anything about your architecture so I couldn't say, but it is not usually the case that a "tens of megabyte" data footprint is "expensive" to generate single-threaded. Single thread mem throughput for 128mb blocks is 22gb/s single-threaded on my AMD, for example.
-
-
yeah I more mean the representation of the file "in editor" is not 1-1 with the file format (it gets decoded into a lot of separate objects when it loads, which then need to be compiled back down into one thing to save it). I just don't want it to hitch every time you click
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.