Sure, patch? This is actually already the request #1922.

Hmm...Well, it does seem to fit the model I discovered, but it was not 
what I expected.  Maybe I was expecting too much for "Monthly:  Recurs 
every _____ month(s) on the same weekday" to be able to discern the 
'last ___day of the month', rather than the 'last ___day in the 4th 
week of the month' or 'last ___day in the 5th week of the month'.



This particular behaviour can cause a lot of extra work to make a 
working schedule, as I had to create two separate 'last ___day of the 
month' events, then manually delete the erroneous scheduled dates 
individually.

Is this something that could be added?  I'm sure I'm not the only 
person in the world who has to work around this type of scheduling.



Thanks,

Warren

This sounds like the expected behavior. There is currently no 
recurrence type that matches the last weekday of a month.

Looking over the recurrences again, it seems that they follow their 
pattern based on the premise of a five-week month, regardless of the 
dates that the days of the month fall.  Therefore, any date scheduled 
for a first or last week date could have this occur...at least that 
seems consistent with what I have observed here.

When setting a monthly recurrence for the last Thursday of each month 
(using Monthly:  Recurs every ____ month(s) on the same weekday), some 
months end up with no event set for the proper last Thursday, some 
months end up with the event on the first Thursday, and some end up 
with both.  The problem seems to happen regardless of which month the 
initial event is created.



BTW, the 'About...' screen in the help window shows my Kronolith 
version as Kronolith H3 (2.1.6).  I didn't see that in the options 
listed.  It is the version that came bundled with the latest stable 
version of Horde Groupware.