BUGS: Pre calendar treats Saturday 1st title of 2nd Saturday, brings also 3rd Saturday as BYMONTHDAY = 21 (but the migration is apparently not)

After having closed the thread of questions related to migration of DTA, I discovered a new failure in the Pre calendar application.  It's using DTA 1.1 and WebOS 1.1, only syncing my Palm profile.  The next of VCALENDAR record is in my migration.mig file (I changed the incorrect initial INTERVAL 1 interval = 12 =):

BEGIN:VCALENDARVERSION:2.0PRODID:Nova-MigrationBEGIN:VEVENTUID:818CATEGORIES:UnfiledCLASS:PUBLICSUMMARY:Woodward Dream CruiseDTSTART:20040821BEGIN:VALARMACTION:DISPLAYTRIGGER:-PT7200MDESCRIPTION:Woodward Dream CruiseEND:VALARMRRULE:FREQ=MONTHLY;INTERVAL=12;BYDAY=3SAEND:VEVENTEND:VCALENDAR

In this case, the initial event occurs on 21/08/2004, which is the 3rd Saturday in August.  Note that August 2004 starts on a Sunday, which I think is German for this particular failure.  This means that Saturday, August 7 is the 1st Saturday in August, not the 2nd.

The migration process initially placed the repetitive event on the thing to the day in 2009, namely, Saturday, August 15, which is the 3rd Saturday.

However, I don't have a five-day-advance alarm today (Monday, 10 August 2009) on my pre (but I had one on my Treo 700 p, which has all my old data calendar loaded on him), so I went to the event on Saturday, 15 August 2009 (where the migration process had placed) and opened it to inspect it.

First of all, I noticed that there are a set of alarm for five days in advance, so I opened the property repeat monthly custom and found that it was set to 'Every month on the 21st [sic]', 'Every 12 months', ' repeat until that Forever. "  It was clearly wrong and does not match the date at which the migration process had placed the event for 2009 (Saturday, August 15, the 3rd Saturday in August 2009).

Even stranger, when I slipped back monthly custom property page repeat (why is there not a Cancel option to get out of these pages without modification?) he must have accepted the 'change' of ' monthly on 21st [translation] "because the event disappeared from where the migration process had placed (August 15, 2009), and it showed on August 21, 2009 , instead.

At this point, I thought that I could access the event initial (21 August 2004) and change the 'monthly on 21st [sic]""monthly on the 3rd Saturday.  That's when I discovered the 2nd (probably related) bug: were the only options available in the event of 'head ':

"Daily".

"Weekly".

"Every month on the 21st [sic]" (enabled)

'Every month on the 4th Saturday' (!)

"Each year the [translation] 21 August [sic]" (geez, it would be really hard to be grammatically correct, you think?)

So, I reached a dead end.  Saturday, August 21, 2004 is clearly not the 4th Saturday, but apparently the Pre calendar program does not know that (again)!

In summary, I documented two bugs:

(1) the "RRULE:FREQ = MONTHLY; RANGE = 12; BYDAY = 3SA"clause contained in the migration.mig file has been munged (it's a term of scientific programming)"every month on the 21st [sic]. "  I don't know if this has been done by the migration process, but it seems unlikely, because the migration process apparently placed the original recurring events on the appropriate dates.  Only after opening one of these events and inspect the property to repeat monthly custom (and getting caught by the Pre Calenar 'feature' of not being able to leave inspecting the property without modifications) made the event move to 21 of every August, as indicated by the property of repeat incorrect on the monthly of custom.

(2) for an event that starts on Saturday, where the month starts on a Sunday, the timing of the front (but apparently not the migration process) is a 'one stop' error and suppose Saturday, March 1st (7) is the 2nd Saturday, and so on.  In the particular case of August 2004, Saturday will eventually be numbered 2 to 5.  I don't know if this is repeated with other days of the week, or what might happen if a particular month ends with the 2nd to 6th (!) a few days of the week to manage.

Anachronistic, PDAGuy, can we bring this to the attention of the Palm development team, please?

Thank you.

After the upgrade to WebOS 1.20, these issues seem to be resolved.  I could go to the entrance of the 'head' and correctly choose the 3rd Saturday in August, every 12 months, and it now appears the correct days in the following years.

Tags: HP Tablets

Similar Questions

Maybe you are looking for