http://bugs.meego.com/show_bug.cgi?id=1266

           Summary: sync-ui: wrong name for device taken from template?
    Classification: MeeGo Projects
           Product: SyncEvolution
           Version: unspecified
          Platform: Netbook
        OS/Version: IA
            Status: ASSIGNED
          Severity: normal
          Priority: Undecided
         Component: GTK UI
        AssignedTo: [email protected]
        ReportedBy: [email protected]
         QAContact: [email protected]
                CC: [email protected],
                    [email protected]
   Estimated Hours: 0.0


pohly <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
               Flag|                            |MeeGo_1.0_Release_Blocker?

Suppose the user has configured an unknown phone manually, for example by
running syncevo-phone-config. When starting the sync-ui and "changing the
service", it shows the existing configuration with the configuration's name in
the list. When unfolding that entry, sync-ui notices that no template has to be
selected for it.

*But* the check boxes say "send/receive changes to/from 'Nokia S40'". When
selecting it, the main window also says "Nokia S40".

"Nokia S40" is wrong in this case, because the device happend to be a Sony
Ericsson K750i. A user already reported this as a bug in 1.0 beta 3.

I suspect that the sync-ui is being clever here and takes the "Nokia S40"
string from a template created for that device. It shouldn't do that. It should
either use the PeerName property or, if not set, the config name.

Likewise, if creating a config for a template, the sync-ui should set the
PeerName, if it doesn't do that already. It can use the name from the template
in that case.

-- 
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.
_______________________________________________
Syncevolution-issues mailing list
[email protected]
http://lists.syncevolution.org/listinfo/syncevolution-issues

Reply via email to