Menu

#21 Initial card review = interval too long

open
nobody
None
5
2006-09-11
2006-09-11
flight16
No

I'm not sure if this is a bug or not, but it seems weird to me.

I've created new cards (that get an interval of three, a creation date of the
date, and a last quizzed date of 1969/1970). When I rate a card a 6, then
look at its details, it shows that the current interval is now around 30
days! A month away. Is this expected?

I only waited about a day before quizzing after the card was drilled and
"right" was selected...

Is the error somewhere around

// Add on the extra days since ideal quiz date, max of 30
if (q > 3) {
qDelta = today - head->qDate;
if (qDelta < 30)
I += (Int32) qDelta;
else
I += 30;
}

The Quiz Date for a new card is 1969/1970, so of course qDelta will be >
30 for the first review.

I don't know enough about the date format it's using, but could we check
for qDate being -1 or 0 (initial values for a new card)?

Discussion

  • Michael Duersch

    Michael Duersch - 2006-09-11

    Logged In: YES
    user_id=1336289

    Yes, that is what is causing the 30 day interval, but I'm
    not sure how it got to that point. It's true that when a
    card is first created, it has a quiz date of 0 (which is
    converted to 1969), but as soon as a card is marked
    memorized, then the quiz date is set to 'today + 1'.

    I've had this code in place for a long time, and I've never
    seen this problem before. Something is causing the quiz
    date to not be set when the card is marked memorized...

     
  • flight16

    flight16 - 2006-09-11

    Logged In: YES
    user_id=667415

    This may or may not be related.

    I have my date format set to YYYY.MM.DD and 24 hour time. When I created a
    card on the palm and imported it back to TwinkEdit, the dates created are Jan
    2007 and Nov 2051. The intervals are both huge negative numbers (which may
    not matter).

     
  • Michael Duersch

    Michael Duersch - 2006-12-13

    Logged In: YES
    user_id=1336289
    Originator: NO

    Have you been able to find a repeatable way that I can reproduce this bug?

     

Log in to post a comment.