-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add undo/redo to webapp #65
Comments
jkomoros
added a commit
that referenced
this issue
Sep 20, 2023
jkomoros
added a commit
that referenced
this issue
Sep 20, 2023
jkomoros
added a commit
that referenced
this issue
Sep 20, 2023
This requires a lot of surgery on reducers/data. I THINK everything seems to mostly work. Note that this does NOT change the peristed data model, just the data model in memory. There are currently no affordances to undo or redo, although versions are available in memory. Part of #65.
jkomoros
added a commit
that referenced
this issue
Sep 20, 2023
jkomoros
added a commit
that referenced
this issue
Sep 20, 2023
jkomoros
added a commit
that referenced
this issue
Sep 20, 2023
…cked issue that event. Part of #65.
jkomoros
added a commit
that referenced
this issue
Sep 20, 2023
This actually activates undoing and redoing in practice, and it appears to roughly work. Part of #65.
jkomoros
added a commit
that referenced
this issue
Sep 20, 2023
jkomoros
added a commit
that referenced
this issue
Sep 20, 2023
jkomoros
added a commit
that referenced
this issue
Sep 20, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Related to #6.
Some way to support undo/redo in the app.
Every operation that modifies any packets (create, delete, change) should go on a state stack. Literally push a new item onto
.packets
and have a currentPacketVersion which stays at 0 when it's at head, and is non-zero when it's not.Pass into packet-editor
canUndo
andcanRedo
.state.data.versionedPackets
be an object with apackets
array, and havegetPacket
know how to handle itstate.data.versionedPacket.currentVersion
= 0The text was updated successfully, but these errors were encountered: