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
47 stars 6 forks source link

changing notetype produces strange results #208

Closed fuquasteve closed 2 months ago

fuquasteve commented 3 months ago

Describe the bug

I messed my ankimorphs deck up a bunch. I don't know if this would be considered a bug, or if it is just something that should be warned about, perhaps in the documentation.

I changed the order of the fields in my notetype. When I did a recalc, the results were strange, and clearly incorrect. I suspect that I should have just made a new row for my modified notetype and then things would have just worded.

Expected behavior

ankimorphs should have read the fields in the changed order and produced logical results.

Screenshots

My setup

Additional context

My deck I am analyzing and modifying with ankimorphs is ridiculously big, 309 000 cards, if this effects anything.

Perhaps this should just be a warning in the documentation, or moving the warning I didn't find to a more prominent position

I set off a cascade of errors with my attempts to correct this problem. There was an easy fix that I finally figured out. I will submit a simple enhancement request that I wish I had had.

mortii commented 3 months ago

Oh wow, that is really, really bad.

This is caused by the settings saving the index of the field instead of always looking it up based on the name/title. I'll fix it asap!

There was an easy fix that I finally figured out. I will submit a simple enhancement request that I wish I had had.

One easy fix right now would be to just save the note filter settings again after you have finished changing the fields of your cards, that way the field index is correct again.

mortii commented 3 months ago

I'm going to do this:

mortii commented 2 months ago

@fuquasteve should be fixed in v2.2.3.

Thanks!

github-actions[bot] commented 2 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.