I'm getting negative numbers in my "Forgotten Cards" field and I think I know why. When I add new cards through the UI, I can choose if I have it memorized at that moment and how many days before I think I will forget. So if I give it a 2,3,4, or 5, it is not considered "Not Memorized", but yet I think it is considered "unseen". As I do my review and grade cards 0 or 1, the negative number of forgotten cards gets closer to zero. But after I eventually get them correct the number goes back.
Is this what is happening? Am I using the software incorrectly? Could you just have a filter that would only allow numbers 0 and greater for that field? I don't think that would actually fix the problem, though. Is it possible to calculate "Unseen in today's batch"? I do appreciate the plug in. I'm happy to send on a copy of my deck for testing if that would help, but I think you could create the same situation On May 29, 6:07 pm, "David A. Harding" <[email protected]> wrote: > On Thu, May 28, 2009 at 10:23:41PM -0700, Meishu wrote: > > "The plugin works, but I don't know Python," > > > Is it technically possible to create a plugin without knowing Python? > > As Peter said, Python isn't too hard, and besides, I have other > programming experience. What I did, anyone with programming experience > can do: backed up my .mnemosyne directory, found a similar plugin, > copied it, then, > > 1. I removed a small piece of code from the copy that I didn't think > would serve my purpose, started Mnemosyne, and determined if the > plugin still worked. If it didn't work, I undid my change and > tried again. If it did work, then I repeated this step. > > 2. After I removed as much unrelated code as I could, I scanned > through Mnemosyne's core code looking for what I needed, copied > it, and pasted it in my plugin as comments. Mnemosyne's core > code is nicely commented, so this isn't as hard as you might > think. > > 3. I uncommented one piece of code, started Mnemosyne, and > determined if the plugin still worked. If it didn't, I changed > the code a little and tried again. If it did work, then I > repeated this step. > > 4. After I got all the parts to work, I simply put them in the order > I needed (forgotten cards = not memorized cards - unseen cards). > > Then it worked and I was happy. I emailed the list to make sure I didn't > accidentally include a function that, say, removes all cards from the > deck on a full moon. > > For a simple user interface change, you should be able to modify an > existing plugin in the way described above. And, as the number of > plugins increases, you'll have more and more examples to draw upon. > > What you don't need to do, which I did, was avoid looking at the Python > manual as a matter of programmer hubris. :) > > Good luck, > > -Dave > -- > David A. Harding Website: http://dtrt.org/ > 1 (609) 997-0765 Email: [email protected] > Jabber/XMPP: [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 -~----------~----~----~----~------~----~------~--~---
