[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[coldsync-hackers] Reporting conduit errors
- To: coldsync-hackers at lusars dot net
- Subject: [coldsync-hackers] Reporting conduit errors
- From: John Deptuch <deptuch+cs at erato dot usask.ca>
- Date: Wed, 17 Sep 2003 11:23:21 -0600
- Reply-to: coldsync-hackers at lusars dot net
- Sender: owner-coldsync-hackers at lusars dot net
Hi
I'm writing a sync (dump and fetch) conduit for a calendaring program that
our department is going to use to replace an aging Windows scheduling
program. Writing it has been pretty painless thanks to Coldsync's excellent
documentation and clean api. We're going to be using Coldsync running in
daemon mode (possibly syncing over the net but I haven't tried that yet). The
only problem that I'm having is that I can't figure out how to report an
error on the Palm. I'm using the following:
die "501 can't open your calendar";
Coldsync show the error on the command line but the Palm reports "HotSync
operation complete" with no errors listed when you press the Log button.
Is there any way to have an error generated on the Palm when a conduit fails?
In order to use Coldsync in daemon mode it would be really nice to have this.
I'm using version 2.3.1 on Debian.
Thanks for your time and for an excellent program.
John Deptuch University of Saskatchewan
This message was sent through the coldsync-hackers mailing list. To remove
yourself from this mailing list, send a message to majordomo@thedotin.net
with the words "unsubscribe coldsync-hackers" in the message body. For more
information on Coldsync, send mail to coldsync-hackers-owner@thedotin.net.