--- Comment #1 from jku <jku(a)linux.intel.com> 2010-07-06 02:15:49 PDT ---
(In reply to comment #0)
Jussi, do you check whether setting up a new phone overwrites an
I fear we'll need an input field for the config name because naming a config
after some unrelated phone just because the template of that phone matches is
unintuitive. Or do we handle that via the PeerName property?
This turned out a bit more complicated than expected... Anyway, current status
* device model name is used as configuration name
* no checking for overwrites is done
Both are problematic, the latter one is a bug that should have been fixed
already, somehow slipped through the cracks.
I've got a fix for both issues that seems to work, but it wasn't as simple as I
hoped. I'll test the configuration setups I can think of and push if it all
There are still edge cases that are not fully working: If you manually setup
two different configurations for the same SyncURL only one will currently be
shown in the UI. This is a result of the device templates getting added after
the configuration UI code was in place... I have an idea how this should be
solved and I'll document that.
Configure bugmail: http://bugs.meego.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.