The idea is that Mnemosyne already shows you the next question, so
that you can start thinking about it, before it saves your database.
Helps with the perceived speed of the program :-) So, the delay is
just the time it takes to show the question. (or in case of the
hanging, forever...)
Peter
Quoting "Michael Campbell" <[email protected]>:
On Wed, Mar 7, 2012 at 1:13 PM, Peter Bienstman
<[email protected]>wrote:
On Wednesday 07 Mar 2012 08:17:10 Scott Youngman wrote:
> 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.
That is not unexpected, because of the delayed writes in libmnemosyne.
Delaying writes (say, until the program exits "normally") for things like
preference changes is a pattern I see often, and universally dislike.
What's the upside, really? I'm getting the impression from previous
emails that mnemosyne does exactly this, and I am curious why.
--
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.
--
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.
