mortii / anki-morphs

A MorphMan fork rebuilt from the ground up with a focus on simplicity, performance, and a codebase with minimal technical debt.
https://mortii.github.io/anki-morphs/
Mozilla Public License 2.0
55 stars 8 forks source link

delete one card should not skip related cards #77

Closed HQYang1979 closed 9 months ago

HQYang1979 commented 9 months ago

image

delete one card should not skip related cards.

I see that when I delete one card (because of bad audio or bad sentence), it shows skipping multiple cards. I am not sure what cards are skipped, but I assume they are related cards. I think only K can skip related cards.

Vilhelm-Ian commented 9 months ago

@HQYang1979 it's not skipping related cards. It's just doing something like the recalc button does

HQYang1979 commented 9 months ago

can it be changed to recalc ing, in order not to cause confusion?

mortii commented 9 months ago

I am not sure what cards are skipped, but I assume they are related cards.

No, AnkiMorphs does not update anything (seen morphs, etc.) when a card is deleted.

There are three ways cards can get skipped after a card is deleted:

  1. The unknown morph on the next card was a name you added to names.txt
  2. The next card has one of the 'known' tags (am-known-manually or am-known-automatically)
  3. You have already seen the unknown morph on the next card, but it was sorted to be after the card you deleted. This happens often; if you use 'L' -key on a card you can see that cards with the same unknown morphs are often not right after each other (the 'New #.....' numbers) . This becomes more and more common the more morphs you know.
HQYang1979 commented 9 months ago

Good to know, thank you very much!

mortii commented 9 months ago

@HQYang1979 This is all great feedback btw, if you are unsure about something then other people will be too. I'll include my explanation it in the guide.

github-actions[bot] commented 6 months ago

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.