https://bugs.meego.com/show_bug.cgi?id=18864
--- Comment #4 from Jussi Kukkonen <[email protected]> 2011-06-14 08:27:04 UTC --- (In reply to comment #2) > Jussi, didn't we also agree that the UI should set the PeerName property if > not > already in the template? We may have done that... > The correct solution would be: > - retrieve template > - set PeerName to the name of the template, if no PeerName is set > - save > - retrieve config > - compare PeerName against template name I guess this requires calling GetConfig for all templates and configs before showing the list of configs/templates... Just to be clear: do you mean we need to 1. match configuration PeerName to template PeerName if both exist 2. match configuration PeerName to template name if the peerName exists 3. match configuration name to template name (insensitively) I tried looking this up but my mail archive probably doesn't go far enough: Do you remember what was the reason for not doing just #3? and why not allow CamelCase config names? -------- Product: OS Middleware Component: SyncEvolution MeeGo Release: 1.2 Severity: trivial Priority: Low Keywords: Status: NEW Who: [email protected] Assigned To: [email protected] Target Build: --- Flags: Changed: -------- https://bugs.meego.com/show_bug.cgi?id=18864 -- Configure bugmail: https://bugs.meego.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching someone on the CC list of the bug. _______________________________________________ Syncevolution-issues mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution-issues
