On Thursday 04 December 2008 11:53:30 notstrom wrote: > Hi thanks for all replies, > > sorry I forgot to mention that. That's exactly what I did; I ran > mnemosyne from a script that appended the current date and time to a > log file each time mnemosyne was run. The last entry before I had to > reset date and time was 18:40 (--as confirmed by the log file--so that > session obviously was okay); then at some point I had to reset date > and time and only after that did I run mnemosyne again (22:00--as > confirmed by the log file). This shouldn't have caused any problems, > should it? > > How exactly does mnemosyne determine whether a new day has come (I > suppose it schedules cards on a day-to-day basis)? From what I have > experienced it does not seem to be 24:00 (Before the date-time issue > it must have been somewhere around 03:00 in the morning and my > suspicion is that this has changed to somewhere around 20:00 after I > had reset date and time). This would seem consistent with the way the > program behaves, at least.....
It's indeed 3am by default. You can change this by editing config.py. Cheers, Peter -- ------------------------------------------------ Peter Bienstman Ghent University, Dept. of Information Technology Sint-Pietersnieuwstraat 41, B-9000 Gent, Belgium tel: +32 9 264 34 46, fax: +32 9 264 35 93 WWW: http://photonics.intec.UGent.be email: [EMAIL PROTECTED] ------------------------------------------------ --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
