I thought you wouldn't be creating a way to directly export back to one, but if you created an exporter, it would have some method like XML with card learning statistics, right? Then I could manually turn around and load it back into 1, and it would even be able to keep things like the close deletion / double-sided cards, though it would lose some of its abilities, like the recognition of sister cards.
Regarding recreating the issue with a new database. I am suspicious, given that everybody else's seemed to freeze, that mine didn't. I did it so quick, though, and I didn't let a day pass for it to attempt to reschedule itself. Perhaps I'll make another dummy one and try and run it for a few days. - Chris. PS. That linux bit blew me away too. I thought if I took such desperate, whole-hearted measures, it would be sure to work fine. You should have seen my stunned reaction when it froze after all. On Tuesday, July 17, 2012 10:25:28 PM UTC-7, Peter Bienstman wrote: > > Quoting Chris <[email protected]>: > > > Scott... that's interesting. My distribution of freezes is much wider, > but > > clusters... so if it starts freezing, it will be something like 2, 2, 4, > 2, > > 3, 2, and then if I give it a day, sometimes I can get through >200 > before > > it freezes... then it starts doing the tight cluster again. I figured > out > > if I screw around with my computer's time/date settings, I can get > through > > many cards. However, I am worried that this might somehow irreparably > > corrupt my database, because I flip it back in time? Maybe Peter would > > know if this is a dangerous method to use? > > I really don't recommend doing this, as it will mess up your > scheduling information. You might even have added a second, different > problem in that way :-) > > > I'll try my cards tonight, and > > get back to you tomorrow... maybe I'll send the database, if I have time > > tomorrow. > > Please do, a database that hangs under Linux is a first for me, and > crucial to help me figure out what's going on, and whether we're > looking at one or at multiple confounding bugs. > > Also, contrary to other people, new dummy databases seem to work in > your case, so if you have a new database which also hangs, that would > rule out the database layer as cause of the problems. > > > Other than that, maybe I'll just have to wait for an export > > feature which will allow me to import back into Ver. 1. > > That's currently not something I plan, as that would result in loss of > information, since there are many features which 1.x simply not > supports. > > I'd rather spend my time fixing the 2.0 issue :-) > > > I'm starting to feel like I'm getting more annoying > > than helpful! > > Please don't, you're certainly not annoying, but crucial in helping > out to figure what's going on. > > Believe me, it's also very frustrating for me, not being able to > reproduce these hangs, and not having any idea how widespread this > problem is. > > Thanks for your continued feedback! > > Cheers, > > 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]. To view this discussion on the web visit https://groups.google.com/d/msg/mnemosyne-proj-users/-/DssMkYW0scAJ. For more options, visit https://groups.google.com/groups/opt_out.
