We will fix this so that the a log entry is added. There will be no
other interaction, since MultiSync is designed to work in the background
and not disturb the user if for example the other end goes down.
Thanks for the report!
/Bo
On Tue, 2003-08-19 at 14:22, Alexander Kirillov wrote:
> No - t
No - the log was empty.
Sasha
On Mon, 2003-08-18 at 23:04, Tom Foottit wrote:
> Thanks for the report. Does the multisync log not contain anything about
> the failure?
>
> Tom
>
>
> On Sun, 17 Aug 2003, Alexander Kirillov wrote:
>
> > Hi,
> > Multisync 0.80 is great but I'd like to point at
Thanks for the report. Does the multisync log not contain anything about
the failure?
Tom
On Sun, 17 Aug 2003, Alexander Kirillov wrote:
> Hi,
> Multisync 0.80 is great but I'd like to point at one shortcoming of it.
> Namely, when using SyncML plugin, multisync doesn't tell you if the
> con
Hi,
Multisync 0.80 is great but I'd like to point at one shortcoming of it.
Namely, when using SyncML plugin, multisync doesn't tell you if the
connection fails. For example, if you typed the hostname wrong, or if
the server is down, multisync statusline would still be "Waiting for
change", and lo
