From efb67941585a82c190302af18d5b6350386ed7da Mon Sep 17 00:00:00 2001
From: Fabian Bumberger <fbumberger@rim.com>
Date: Wed, 25 Sep 2013 11:44:33 +0200
Subject: QNX: Extend documentation for NDEF message handlers

Change-Id: If96b4fc9aacc3c16e9e8eb88ab4849ec15e280b5
Reviewed-by: Alex Blasche <alexander.blasche@digia.com>
---
 src/nfc/qnearfieldmanager.cpp | 15 +++++++++++++++
 1 file changed, 15 insertions(+)

diff --git a/src/nfc/qnearfieldmanager.cpp b/src/nfc/qnearfieldmanager.cpp
index 5e483343..f2fafdce 100644
--- a/src/nfc/qnearfieldmanager.cpp
+++ b/src/nfc/qnearfieldmanager.cpp
@@ -108,6 +108,21 @@ QT_BEGIN_NAMESPACE
         manager->registerNdefMessageHandler(this,
                                             SLOT(handleNdefMessage(QNdefMessage,QNearFieldTarget)));
     \endcode
+
+    On BlackBerry the registration for NDEF message handlers is done over the
+    \l{https://developer.blackberry.com/native/documentation/core/invocation_framework.html}{Invocation Framework}.
+    This means that the application has to set an invoke target in the bar descriptor xml file when using
+    \l registerNdefMessageHandler().
+
+    \code
+    <invoke-target id="com.myapp.id">
+        <type>APPLICATION</type>
+        <filter>
+            <action>bb.action.OPEN</action>
+            <mime-type>application/vnd.rim.nfc.ndef</mime-type>
+        </filter>
+    </invoke-target>
+    \endcode
 */
 
 /*!
-- 
cgit v1.2.3