From: Roger B. <ro...@ro...> - 2004-05-11 02:23:55
|
Peter Dufault wrote: > First thing I noted is that though the entry I created at bitpim the > other day is sent back and forth to the phone, the phone doesn't see > it. Yes, that is because the calendar file is in a different format. There is no sync protocol for the calendar. BitPim just reads and writes a file on the filesystem. Being able to do so doesn't mean the file is valid for the phone. > Secondly I created a simple entry on the phone (Text "test" from 2:00 > to 3:00 PM today) and then tried to get the calendar using BitPim. I > received this message on the startup terminal screen: > FutureWarning: x<<y losing bits or changing sign will return a long in > Python 2.4 and up > res|=buf.getnextbyte()<<shift Ignore all warnings like that. They are very annoying but it is not a bug in the code. It looks like they have made each record one byte longer. Please delete the calendar files as detailed in my earlier message http://article.gmane.org/gmane.comp.mobile.bitpim.devel/229 and reboot the phone. Then make some events where the name is as long as possible. See if you can figure out where the extra byte(s) went. The existing description is in p_lgvx4400 as scheduleevent. Roger |