diff options
author | Fabian Bumberger <fbumberger@rim.com> | 2013-09-25 11:44:33 +0200 |
---|---|---|
committer | The Qt Project <gerrit-noreply@qt-project.org> | 2013-09-25 18:20:12 +0200 |
commit | efb67941585a82c190302af18d5b6350386ed7da (patch) | |
tree | b634d2dbd6f18afe6f5f8990fb6fcecdd9281db3 | |
parent | c08bd2c68b32d44269374753d66fe3cb934f16e0 (diff) |
QNX: Extend documentation for NDEF message handlersv5.2.0-alpha1
Change-Id: If96b4fc9aacc3c16e9e8eb88ab4849ec15e280b5
Reviewed-by: Alex Blasche <alexander.blasche@digia.com>
-rw-r--r-- | src/nfc/qnearfieldmanager.cpp | 15 |
1 files changed, 15 insertions, 0 deletions
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 */ /*! |