langfingaz/anki
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
fd324d4711
anki/ftl/core/undo.ftl

23 lines
602 B
Plaintext
Raw Normal View History

undo unbury/unsuspend
2021-03-04 13:14:35 +01:00
undo-undo = Undo
undo-redo = Redo
add undo.ftl
2021-03-03 09:57:45 +01:00
# eg "Undo Answer Card"
undo-undo-action = Undo { $val }
# eg "Answer Card Undone"
note deletion undo; refactoring - transact() now automatically clears card queues unless an op opts-out (and currently only AnswerCard does). This means there's no risk of forgetting to clear the queues in an operation, or when undoing/ redoing - CollectionOp->UndoableOp - clear queues when redoing "answer card", instead of clearing redo when clearing queues
2021-03-05 10:09:08 +01:00
undo-action-undone = { $action } undone
add undo.ftl
2021-03-03 09:57:45 +01:00
undo-redo-action = Redo { $action }
note deletion undo; refactoring - transact() now automatically clears card queues unless an op opts-out (and currently only AnswerCard does). This means there's no risk of forgetting to clear the queues in an operation, or when undoing/ redoing - CollectionOp->UndoableOp - clear queues when redoing "answer card", instead of clearing redo when clearing queues
2021-03-05 10:09:08 +01:00
undo-action-redone = { $action } redone
undo support for bulk tag add/remove
2021-03-05 11:47:51 +01:00
## Action that can be undone
add undo.ftl
2021-03-03 09:57:45 +01:00
undo-answer-card = Answer Card
undo unbury/unsuspend
2021-03-04 13:14:35 +01:00
undo-unbury-unsuspend = Unbury/Unsuspend
undo support for deck adding/removing Work in progress - still to do: - renames appear as 'Update Deck' - easiest way to solve it would be to have a separate backend method for renames - drag&drop of decks not yet undoable - since the undo status is updated after the backend method ends, the older checkpoint() calls need to be replaced with an update_undo_status() at the end of the call - if we just remove the checkpoint, then the menu doesn't get updated
2021-03-10 14:50:11 +01:00
undo-add-deck = Add Deck
undo support for note adding
2021-03-05 01:04:42 +01:00
undo-add-note = Add Note
undo support for bulk tag add/remove
2021-03-05 11:47:51 +01:00
undo-update-tag = Update Tag
make mark toggling undoable - note.flush() behaves like before, as otherwise actions or add-ons that perform bulk flushing would end up creating an undo entry for each note - added col.update_note() to opt in to the new behaviour - tidy up the names of some related routines
2021-03-05 13:45:55 +01:00
undo-update-note = Update Note
make flag changes in the reviewer undoable This splits update_card() into separate undoable/non-undoable ops like the change to notes in b4396b94abdeba3347d30025c5c0240d991006c9 It means that actions get a blanket 'Update Card' description - in the future we'll probably want to either add specific actions to the backend, or allow an enum or string to be passed in to describe the op. Other changes: - card.flush() can no longer be used to add new cards. Card creation is only supposed to be done in response to changes in a note's fields, and this functionality was only exposed because the card generation hadn't been migrated to the backend at that point. As far as I'm aware, only Arthur's "copy notes" add-on used this functionality, and that should be an easy fix - when the new note is added, the associated cards will be generated, and they can then be retrieved with note.cards() - tidy ups/PEP8
2021-03-06 15:17:17 +01:00
undo-update-card = Update Card
undo support for deck adding/removing Work in progress - still to do: - renames appear as 'Update Deck' - easiest way to solve it would be to have a separate backend method for renames - drag&drop of decks not yet undoable - since the undo status is updated after the backend method ends, the older checkpoint() calls need to be replaced with an update_undo_status() at the end of the call - if we just remove the checkpoint, then the menu doesn't get updated
2021-03-10 14:50:11 +01:00
undo-update-deck = Update Deck
make 'forget card' undoable; remove checkpoint() in set_due_date
2021-03-12 07:13:50 +01:00
undo-forget-card = Forget Card
more reset refactoring 'card modified' covers the common case where we need to rebuild the study queue, but is also set when changing the card flags. We want to avoid a queue rebuild in that case, as it causes UI flicker, and may result in a different card being shown. Note marking doesn't trigger a queue build, but still causes flicker, and may return the user back to the front side when they were looking at the answer. I still think entity-based change tracking is the simplest in the common case, but to solve the above, I've introduced an enum describing the last operation that was taken. This currently is not trying to list out all possible operations, and just describes the ones we want to special-case. Other changes: - Fire the old 'state_did_reset' hook after an operation is performed, so legacy code can refresh itself after an operation is performed. - Fire the new `operation_did_execute` hook when mw.reset() is called, so that as the UI is updated to the use the new hook, it will still be able to refresh after legacy code calls mw.reset() - Update the deck browser, overview and review screens to listen to the new hook, instead of relying on the main window to call moveToState() - Add a 'set flag' backend action, so we can distinguish it from a normal card update. - Drop the separate added/modified entries in the change list in favour of a single entry per entity. - Add typing to mw.state - Tweak perform_op() - Convert a few more actions to use perform_op()
2021-03-14 10:54:15 +01:00
undo-set-flag = Set Flag
support undo of filtered deck build/empty
2021-03-24 03:56:06 +01:00
undo-build-filtered-deck = Build Deck
Reference in New Issue Copy Permalink