weekly recurrence behaves a little strange and definitely differs from daily recurrence when N > 1
let me explain; imagine yourself a 3 month view like this:
| Code: |
October November December
KW M T W T F S S KW M T W T F S S KW M T W T F S S
39 1 2 3 44 1 2 3 4 5 6 7 48 1 2 3 4 5
40 4 5 6 7 8 9 10 45 8 9 10 11 12 13 14 49 6 7 8 9 10 11 12
41 11 12 13 14 15 16 17 46 15 16 17 18 19 20 21 50 13 14 15 16 17 18 19
42 18 19 20 21 22 23 24 47 22 23 24 25 26 27 28 51 20 21 22 23 24 25 26
43 25 26 27 28 29 30 31 48 29 30 52 27 28 29 30 31
|
Starting from 01.10.2010: (always first entry)
+ a 1 weekly recurrence event
number of recurrences: 9
---->> 9 Entries, last on 26.11.2010 OKAY!
+ a 3 weekly recurrence event
number of recurrences: 9
---->> 3 Entries, last on 12.11.2010
+ a 3 weekly recurrence event
number of recurrences: 10
---->> 4 Entries, last on 03.12.2010
+ a 2 weekly recurrence event
number of recurrences: 8
---->> 4 Entries, last on 12.11.2010
+ a 2 weekly recurrence event
number of recurrences: 9
---->> 5 Entries, last on 26.11.2010
whats the reason for the strange time-math?
number of entries = INTEGER_CEILING( number of recurrences / weekly-step )
should't it be:
number of entries = number of recurrences
covered time = number of recurrences * weekly-step
because:
in a 2 daily recurrence event, with
number of recurrences: 9
you get 9 Entries, last on 17.10.2010
so the covered time = number of recurrences * daily-step = 9 * 2 = 18 days
Regards,
LarsS
PS: if this proves 2b a real bug, i used Rainlendar-Lite-2.7b91-32bit.exe for this
