Hi everyone, recent CVS versions of the opie_sync plugin for multisync now include support for interacting with the QCop bridge that is part of Opie (and Qtopia), rather than going into detail on what it exactly is I'd like to outline what it can do for you:
- Bring up the "Syncing" screen on your Opie/Qtopia device to keep you from interfering with the sync process. - Properly sync regardless of the status of the PIM apps, i.e. you no longer have to quit them after making changes to have the sync pick those up. This includes being able to leave PIM apps quickloaded without having to worry about anything going amiss. - In the future opie_sync will properly deal with Opie/Qtopia installations running as non-root users and automatically use the user's home directory to sync the PIM data to/from, even enabling different users to keep distinct contacts/todos/appointments. Here's the catch: Due to its recent introduction the functionality is not very well tested, that's where we need your help. Anyone willing to help testing should do the following: - Get the most recent CVS tarball from the multisync homepage, the public CVS version will not do, as it can be several days(!) behind the tarballs. - Build multisync, opie_sync and all other plugins you require, open the configuration dialog for the opie_sync plugin and make sure that "Enable QCop" is checked. - Sync. On the first attempt please watch your Opie/Qtopia device, it might ask you for permission to sync. - Use it. Use it some more. Send bug reports to me or to this list. - Play around with it. Have any combination of datebook/addressbook/todolist running/quickloaded and see if you can find any quirks. - In particular I'm interested in knowing what happens when you sync twice in a row with datebook opened/quickloaded. ATTENTION: This *may* crash Opie and drop you to a command line, make sure you loose no important data in the process. I am fairly certain that this behaviour is an Opie bug, but I'd like to pinpoint the affected version/architecture(s), between Tom and me it works fine on this IPaq and bombs out on my SL-5500G with OZ 3.2 and Opie 1.0 which is not nearly big enough of a sample to say anything. In every report, please include a description of the steps you took to cause the bug. For now, please don't report if you can not reliably reproduce the behaviour. With *each* report please, please, please let me know what device you use, which distribution you run on it and which version of Opie/Qtopia is concerned. If you feel comfortable enough with gdb feel free to include a stack backtrace. Please note that multisync is a multithreaded application and most likely thread "2" is the one of interest. If in doubt: if it spits out line numbers from opie_*.c files you are likely to be on target. I'm looking forward to your input! Regards, Eike -- Eike M. Lang <[EMAIL PROTECTED]> ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Multisync-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/multisync-users
