Sorry, I didn't mean to imply that the endless loop of the same two cards was part of the problem. It was just the motivation to delete the first card in order to break the cycle. I think the loop was due to the program hanging before it could record any change in the database, hence it restarted from the exact same condition (grades and ordering of cards for review) as before the crash.
And that is a characteristic which I have not mentioned previously, so I will generalize it here: if C, D, and E are sequential cards in review and the program hangs on E, then the last review grade or status for D will not be registered in the database. The evidence for that is when the program is restarted, the number of scheduled and not memorised cards shown in the status bar will revert to the number shown after card C was reviewed. (The development version I am using is dated February 23 13:50.) On Mar 7, 7:19 am, Peter Bienstman <[email protected]> wrote: > > 1) Mnemosyne keeping on repeating the same two cards. This I should have > solved in the development version last week -- 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 this group at http://groups.google.com/group/mnemosyne-proj-users?hl=en.
