Donate Share

Twinkle Flashcards

Code

Programming Languages: Java, C

License: GNU General Public License (GPL)

Repositories

browse code, statistics, last commit on 2007-05-13 svn co https://twinkle.svn.sourceforge.net/svnroot/twinkle twinkle

browse code, statistics, last commit on 2007-05-13 cvs -d:pserver:anonymous@twinkle.cvs.sourceforge.net:/cvsroot/twinkle login

cvs -z3 -d:pserver:anonymous@twinkle.cvs.sourceforge.net:/cvsroot/twinkle co -P modulename

Show:

What's happening?

  • korean language support

    I'd love to be able to move to Twinkle instead of Supermemo which I'm using now, but I need a Korean encoding to convert my cards. Thanks for all your work. Ron Knickerbocker ron_kb2yahoo.com.

    2008-02-10 13:35:48 UTC by nobody

  • Crash when assigning buttons

    My PalmIIIe OS3.1.1 crashes when trying to assign hardware key bindings. I get a "Fatal Exception" upon touching the Assign button. ---- My PalmVx OS 3.5.0 also crashes when assigning buttons. Here I can assign buttons, Hard1, Hard2... are all acknowledged (even Power and Contrast!). But crashes upon exit. I did notice that depending on the exit, the bindings may or may not be saved.

    2007-12-29 02:03:05 UTC by wallylynn

  • Comment: A crash on database merge

    I'm also experiencing odd behavior with database merges: Palm Vx OS 3.5.0. Hard reset and installed Twinkle 1.0.1. Create two databases and try to merge them: Fatal Exception (no info). No confirmation question. Requires pin-in-back reset. Both Databases still usable and untouched. I've not found a work around. 0 cards, 1 card, multiple, all causes the crash. Renaming by itself...

    2007-12-29 01:47:52 UTC by wallylynn

  • Comment: cards not truly deleted

    Oh, I just noticed that selecting to create a new card, but not entering it also has the same problem. Don't press "New" unless you mean it. Further playing between my two palmpilots leads me to believe that database merging is it's own weird bugs.

    2007-12-29 01:24:03 UTC by wallylynn

  • Comment: cards not truly deleted

    Hmm, maybe this related to: [ 1544265 ] A crash on database merge .

    2007-12-26 16:29:59 UTC by wallylynn

  • Comment: cards not truly deleted

    The merging suggestion resulted in "Fatal Alert: nil value" on my PalmIIIe. Twinkle crashed requiring a soft reset upon the rename, and subsequently on trying to start Twinkle. The old database was no longer on my palmpilot. I forgot to check the number of records in the new database, but I had to delete the remaining new database for Twinkle to start. I'll retest some other combinations...

    2007-12-26 15:56:05 UTC by nobody

  • Comment: cards not truly deleted

    OK, After a very quick look, it looks like the function dbDeleteCard() in dbUtils.c needs to use DmRemoveRecord rather than DmDeleteRecord. Issue of using DmDeleteRecord without having a proper conduit (not standard backup conduit) is discussed here: http://www.mail-archive.com/palm-dev-forum@news.palmos.com/msg36757.html For now, I wouldn't panic about it. One more workaround to try...

    2007-12-23 21:28:26 UTC by k_uber

  • Comment: cards not truly deleted

    At the moment, instead of hotsyncing, I use a daily automated backup program to the built-in SD card (NVBackup). I tend to use TwinkEdit only for creating databases initially. When I create a database, I beam it to the Treo by Bluetooth or copy it to the SD Card. Now and then I back up the data just by copying the SD card contents. When I want to add cards to an existing database, I normally...

    2007-12-23 21:10:43 UTC by k_uber

  • Comment: cards not truly deleted

    I tried the hotsync suggestion but it didn't work. The deleted cards are still counted and the number of records remained the same. May I ask, since you don't hotsync, what do you do?.

    2007-12-23 20:05:09 UTC by wallylynn

  • Comment: cards not truly deleted

    Confimed same issue on Treo 650. Does this fix itself after a hotsync? (I don't use hotsync) The normal delete behaviour for palm databases is that they are 'marked as deleted' and then actually deleted when the conduits run at hotsync. This gives desktop conduits access to the information for backup purposes. But I don't know if that is what's happening here. It may just be counting all of...

    2007-12-21 17:00:16 UTC by k_uber

Our Numbers