Use enumerations for detail types and detail fields.

This patch changes the internal representation of detail
types and field names within details from a string-based
representation to enum constants.
Detail definition names are then replaced by the
concept of "Detail Type".
Enum values are also aligned across C++ Vs QML APIs

Authors:
- Tommi Anttila <tommi.4.anttila@nokia.com>
- Claudio Brunelli <claudio.brunelli@nokia.com>
- Cristiano di Flora <cristiano.di-flora@nokia.com>

Change-Id: I8b86022d08f9c3baf84b658f07e6600efdc73b8b
Reviewed-by: Cristiano di Flora <cristiano.di-flora@nokia.com>
Reviewed-by: Claudio Brunelli <claudio.brunelli@nokia.com>

1 files changed, 2 insertions, 2 deletions

diff --git a/src/imports/contacts/qdeclarativecontact_p.h b/src/imports/contacts/qdeclarativecontact_p.h
index 74a1aae11..96a806144 100644
--- a/src/imports/contacts/qdeclarativecontact_p.h
+++ b/src/imports/contacts/qdeclarativecontact_p.h
@@ -179,10 +179,10 @@ private slots:
 private:
     Q_DISABLE_COPY(QDeclarativeContact)
 
-    template<typename T> T* getDetail(const QDeclarativeContactDetail::ContactDetailType &definitionName)
+    template<typename T> T* getDetail(const QDeclarativeContactDetail::DetailType &type)
     {
         foreach (QDeclarativeContactDetail *detail, m_details) {
-            if (definitionName == detail->detailType())
+            if (type == detail->detailType())
             {
                 T* tempDetail = static_cast<T *>(detail);
                 return tempDetail;