various problems with Palm beta and Missing Sync, especially
I am having several different problems with LB on my Palm TX. Some started after installing Missing Sync and the LB beta, one started before installing either.
1. I'm getting some "assertion error" messages. What are assertion errors?
2. I am getting error messages when I switch from LB to Datebk, telling me that there is an error in the end date for a specific repeating event (the specific event changes each time I switch to Datebk). After I get the error message, I find that whatever event was mentioned in the error message is now repeating every single day. Each time, it's an event that I had originally set to repeat daily for two or three days. Actually, I think I made this one go away, by deleting the repeating event in Datebk each time I entered Datebk, until all of them were gone. -- It's hard to explain!
3. This last problem started before I installed the LB beta or Missing Sync. I am having trouble with repeating todos getting duplicated when I sync between Palm and Mac. So, for instance, if I have a todo to "update web site" which repeats weekly, after a sync I'll suddenly have it show up two or three -- or even five or six -- times on a single day.
I am also having problems with syncing to iCal (for instance, getting the Tasks on my Palm deleted for me), but I've turned off those conduits for now and I'll deal with that later. It is more important to me to get the LB and Datebk sync issues figured out first!
Hmmmmm. My signature file seems to have disappeared. If it were showing up, it would say -- Mac running 10.4.11, LB 4.whatever beta, now Missing Sync, Datebk 6.1a, r4
Comments
Assertions are a beta message...
Assertions are places in the beta code, where we say "I don't think this can happen... but, if it does, I want to know about it...." They are automatically stripped out of release builds, and you never see them in release builds.
Sometimes assertion messages are very important, and indicate a potential crashing situation, and sometimes the are very minor... like a drawing routine is off by a pixel in an obscure region. Sometimes there is something unexpected in the data, like we think we're getting a task that is supposed to be at top level with child tasks, and the Outline level is set to "2"... that's not consistent, and we need to know about that to figure out what to do to make it consistent. For those kinds of problems, we usually need a copy of the data file to track it down under the debugger.
So... generally, for asserts, it really helps us, if you can let us know what platform you get the assert on, what it was doing, and the exact message, then we can figure out what to do about it. And knowing which beta version on the Mac helps too, because the code here is a living breathing thing and we may have already fixed the issue that you are tripping over.
Best wishes,
--Catherine--*
Ah-hah, there's my sig file
Ah-hah, there's my sig file back again. :-)
All the assertion errors so far have been on the Palm. If I get any more of them, I'll try to note them down and report them to you. Thanks for your time!
-- amazondoc --
Confused, bemused, and disorganized, but trying to reform!
Palm TX, Pismo running OS 10.4.11, LB 4.1b3, Datebk 6.1a r4, Missing Sync 6.0.3
After further testing, it
After further testing, it appears that the errors have stopped since I disabled the iCal conduits in Missing Sync. I have not yet gotten any more of the assertion errors, nor the duplicating task errors.
I will keep testing the beta without iCal sync for at least several days, then turn those conduits back on and see what happens. Stay Tuned.
-- amazondoc --
Confused, bemused, and disorganized, but trying to reform!
Palm TX, Pismo running OS 10.4.11, LB 4.1b3, Datebk 6.1a r4, Missing Sync 6.0.3