On Wed, 2007-06-06 at 23:39 +0100, Jonny Lamb wrote: > On Wed, 2007-06-06 at 23:12 +0100, Mark Ellis wrote: > > Aha, I'll explain my reasoning. I'm just thinking short term fix here, > > as a transition until odccm has pre WM5 support (maybe). odccm is the > > preferred option for WM5, but currently for a complete solution vdccm is > > needed for pre WM5. vdccm interferes with odccm because it has some WM5 > > support. Disable WM5 in vdccm to have optimal support for both pre > > (vdccm) and WM5 (odccm) on the same machine. > > Yes that's okay, but although odccm is "preferred", if I had both a > WM2003 device and a WM5 device, I would simply use vdccm. I wouldn't use > two daemons for essentially the same thing.
Ok, that's fair enough, I wasn't sure how good the WM5 support was in vdccm. > > I also think that disabling simply WM5 support in vdccm will be harder > than it sounds.. Having had a look at it I think you're probably right on that one. ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ SynCE-Devel mailing list SynCE-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/synce-devel
