1 No support for BlackBerry Z10 and newer devices
2 -----------------------------------------------
3 I don't have one of these devices, and from what I understand,
4 the protocol is completely different. User reports
8 Desktop GUI does not display or edit some recurring calendar entries correctly
9 ------------------------------------------------------------------------------
10 Some recurring calendar entries, such as birthdays, have 0 value
11 start and end times, but use the recurring mode YearByDate to
12 specify the day of the birthday. This is not handled correctly,
13 if at all, in the Desktop GUI, and merely shows todays date
14 in the Start and End fields, and does not display the month or
15 day number of the recurring YearByDate at all.
17 This requires a GUI modification, and additional code to handle the
21 Tasks database self-corrupts on many devices
22 --------------------------------------------
23 If you extract a Tasks record, and then write it back via
24 SetRecordByIndex(), on many devices that I tested, it ends up
25 corrupting the record on the device, and the GUI on the device
26 appears messed up. (It shows the first few fields twice)
27 Such a corrupt record also loses the due date.
29 This appears to be a bug in the device firmware.
31 The workaround, when working with the Tasks database, is to
32 first DeleteByIndex() and then AddRecord() via the Desktop mode class,
33 using the same record ID. This works, but is unfortunately
36 See the Desktop GUI and the opensync plugins for examples of this
39 Ideally, we should test a Tasks sync on Windows, and see how
40 the Windows software handles this. There may be some protocol
41 changes that will be needed in future Barry versions.
44 Dates before 2007/01/01 use modern DST rules
45 --------------------------------------------
46 This is a device firmware issue. Most devices that I've tested
47 use modern DST rules (i.e. DST begins second Sunday in March)
48 for all dates, even though these new rules only came into effect
49 in 2007. So dates in 2006 and earlier have a window of innaccuracy,
50 since dates are given to Barry in UTC, converted to time_t, and most
51 computer systems will then convert that time_t to local time using
52 the old DST rules, and be an hour off.
54 Barry does nothing to workaround this bug, since most dates
55 are used in Calendar and Task apps, which usually only matter
56 for modern dates. In other words, you use the Task and Calendar
57 apps to remind yourself of future appointments, not the past.
58 This appears to be the logic that RIM used as well, since the
59 device seems to only have one DST rule, and doesn't care about