Mark Ellis
2008-05-06 09:09:27 UTC
Tested today with synce-hal + WM 6.1; all works OK :-)
One moment: probably the message "Authorization failed, disconnect device and connect again" should be changed for WM6-based devices, because reaching this part of code when working with them means just waiting for password on device, not fatal authorization error. Just to make process flow more clear for new users...
For example, "Waiting for password on device..." or something like that.
--
Hi IlyaOne moment: probably the message "Authorization failed, disconnect device and connect again" should be changed for WM6-based devices, because reaching this part of code when working with them means just waiting for password on device, not fatal authorization error. Just to make process flow more clear for new users...
For example, "Waiting for password on device..." or something like that.
--
I hadn't forgotten you, just a bit busy. Yes, this needs looking at, I
couldn't see a quick fix way of doing it though. It'll need a bit of
work.
Ta
Mark
-----Original Message-----
Sent: 24 апреля 2008 г. (четверг) 03:14
Subject: Re: sync-engine password-protected WM6 issue.
you're the expert, does this look ok ?
I'll have a chance to try this with some hardware tomorrow. It seems to
check everything it needs to before calling OnConnect() and it looks
basically sound. I think it is probably sound enough to commit it for
wider testing.
John.
Ok, I've committed this to see how it survives in the world :)
[The entire original message is not included]
Sent: 24 апреля 2008 г. (четверг) 03:14
Subject: Re: sync-engine password-protected WM6 issue.
You're right, it shouldn't change, except for the locked to unlocked
changed when you authenticate. The problem is that WM5 can be unlocked
directly by the sync-engine auth procedure (and also indirectly if
something else authenticates) while WM6 is always a more indirect
process.
Ok, this looks ok, and works with WM5, can you try it with WM6. John,changed when you authenticate. The problem is that WM5 can be unlocked
directly by the sync-engine auth procedure (and also indirectly if
something else authenticates) while WM6 is always a more indirect
process.
you're the expert, does this look ok ?
check everything it needs to before calling OnConnect() and it looks
basically sound. I think it is probably sound enough to commit it for
wider testing.
John.
[The entire original message is not included]