Currently undo/redo data is stored naively, implement a dynamic storage of text for it #165
Assignees
Labels
enhancement
New feature or request
Comments
AngryFender
added a commit
that referenced
this issue
Jun 4, 2024
…edited for undo/redo. Created EditType for each unique actions that user can do to edit text. Only data/text relevent to the EditType will to stored witth the logic that goes with undo/redo.
AngryFender
added a commit
that referenced
this issue
Jun 5, 2024
AngryFender
added a commit
that referenced
this issue
Jun 6, 2024
… blocks or all the blocks in the raw document according to the new edit types
AngryFender
added a commit
that referenced
this issue
Jun 7, 2024
AngryFender
added a commit
that referenced
this issue
Jul 20, 2024
…e the rawDocument with old and new texts. Also corrected the position of text cursor after redo action was performed. Also added checks to stop undo/redo actions if out of limit
AngryFender
added a commit
that referenced
this issue
Jul 20, 2024
…ine correctly updates the rawDocument with old and new texts, check if the position of text cursor after redo/undo was set properly and check to stop undo/redo actions if out of limit
AngryFender
added a commit
that referenced
this issue
Jul 20, 2024
…ructor of the EditCommand. Also for single block edits only the edit blocks are now stored in the undo/redo command instead of storing the whole file.
AngryFender
added a commit
that referenced
this issue
Jul 21, 2024
…ing from hiding but to show when applying mk effects on all the blocks. This gives better control during undo/redo where the block number isn't same as the current block number of the text cursor
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
No description provided.
The text was updated successfully, but these errors were encountered: