On Friday, July 09, 2010 11:56:38 am Gwern Branwen wrote: > I have noticed that while C-s and File->Save both seem to flush > changes to disk (something I do fairly often as I work, as I have said > previously, on a very unreliable laptop), but C-s seems to sync much > faster than File->Save - Mnemosyne returns to usability so quickly > that I was initially suspicious that it was not working at all until I > checked the mtimes on .mnemosyne/default.mem, but with File->Save, > there is a very visible lag where Mnemosyne's window is frozen and not > redrawn, and the plugin output in the statusbar disappears to reappear > after Mnemosyne unfreezes. > > What's up with that?
That's rather strange, as the underlying code that get executed is exactly the same in both case. The only thing that is different is the pathway through the GUI code, and that's not something I can do much about... 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 this group at http://groups.google.com/group/mnemosyne-proj-users?hl=en.
