Quoting [email protected]:
- you decide to start learning the 'camping' category before 'food and kitchen' category and so you don't learn the work 'knife' because the software didn't allow you to encode it under 'camping' as you have already encoded it in 'food and kitchen'.
I had not considered this use case, but you have a valid point here. In the future, I will change this to a dialog box which allows the user to set his preferred cause of action for this card.
In the meantime, as a workaround, you can create clones of the card type you are using, so e.g. have a camping card type, a food card type, etc, as the duplicate preventention mechanism works on the card type level. Later, when I update the duplicate handling, you can then move this cards back to their original card type.
Suggestions for duplicates improvement at import: - detect potential duplicates
On my todo list.
Suggestions for Mnemosyne settings improvement: - check box for "Allow duplicates at import" - check box for "Allow duplicates when encoding a new card" - check box for "Warning message when encoding a duplicated card"
I think that would lead to too many settings and confusion. I prefer showing a dialog box when this occurs where the user could pick his preferred action.
Thanks for the feedback and helping make Mnemosyne better! Peter -- You received this message because you are subscribed to the Google Groups "mnemosyne-proj-users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
