| android |
|
|
- |
| ApiChangesQt6.txt |
|
1662 |
- |
| CMakeLists.txt |
|
3983 |
- |
| configure.cmake |
|
585 |
- |
| doc |
|
|
- |
| ios |
|
|
- |
| ndef |
|
|
- |
| neard |
|
|
- |
| pcsc |
|
|
- |
| qapduutils.cpp |
Utilities for handling smart card application protocol data units (APDU).
The structure of APDUs is defined by ISO/IEC 7816-4 Organization, security
and commands for interchange. The summary can be found on Wikipedia:
https://en.wikipedia.org/wiki/Smart_card_application_protocol_data_unit
|
2387 |
- |
| qapduutils_p.h |
|
1269 |
- |
| qndeffilter.cpp |
|
15914 |
- |
| qndeffilter.h |
|
1489 |
- |
| qndefmessage.cpp |
!
\class QNdefMessage
\brief The QNdefMessage class provides an NFC NDEF message.
\ingroup connectivity-nfc
\inmodule QtNfc
\since Qt 5.2
A QNdefMessage is a collection of 0 or more QNdefRecords. QNdefMessage inherits from
QList<QNdefRecord> and therefore the standard QList functions can be used to manipulate the
NDEF records in the message.
NDEF messages can be parsed from a byte array conforming to the NFC Data Exchange Format
technical specification by using the fromByteArray() static function. Conversely QNdefMessages
can be converted into a byte array with the toByteArray() function.
|
10350 |
- |
| qndefmessage.h |
|
1437 |
- |
| qndefnfcsmartposterrecord.cpp |
!
\class QNdefNfcIconRecord
\brief The QNdefNfcIconRecord class provides an NFC MIME record to hold an
icon.
\ingroup connectivity-nfc
\inmodule QtNfc
\since Qt 5.2
This class wraps the image data into an NDEF message.
It provides an NDEF record of type \l QNdefRecord::Mime.
The \l {QNdefRecord::}{payload}() contains the raw image data.
|
20584 |
- |
| qndefnfcsmartposterrecord.h |
|
3761 |
- |
| qndefnfcsmartposterrecord_p.h |
|
2131 |
- |
| qndefnfctextrecord.cpp |
!
\class QNdefNfcTextRecord
\brief The QNdefNfcTextRecord class provides an NFC RTD-Text.
\ingroup connectivity-nfc
\inmodule QtNfc
\since 5.2
RTD-Text encapsulates a user displayable text record.
|
4249 |
- |
| qndefnfctextrecord.h |
|
959 |
- |
| qndefnfcurirecord.cpp |
!
\class QNdefNfcUriRecord
\brief The QNdefNfcUriRecord class provides an NFC RTD-URI.
\ingroup connectivity-nfc
\inmodule QtNfc
\since 5.2
RTD-URI encapsulates a URI.
|
2472 |
- |
| qndefnfcurirecord.h |
|
774 |
- |
| qndefrecord.cpp |
!
\class QNdefRecord
\brief The QNdefRecord class provides an NFC NDEF record.
\ingroup connectivity-nfc
\inmodule QtNfc
\since 5.2
QNdefRecord and derived classes are used to parse the contents of
\l {QNdefMessage}{NDEF messages} and create new NDEF messages.
Use typeNameFormat() and setTypeNameFormat() to
get and set the type name format of the NDEF record.
Use type() and setType() to get and set the type of the NDEF record.
Use id() and setId() to get and set the id of the NDEF record.
Use payload() and setPayload() to get and set the NDEF record payload. isEmpty() can be used
to test if the payload is empty.
QNdefRecord is an implicitly shared class. This means you can efficiently convert between
QNdefRecord and specialized record classes. The isRecordType() template function can be used
to test if a conversion is possible. The following example shows how to test if a QNdefRecord
is an NFC RTD Text record and extract the text information from it.
\snippet nfc.cpp Record conversion
\section1 Creating Specialized NDEF Record Classes
Specialized NDEF record classes can be easily created with the Q_DECLARE_NDEF_RECORD() and
Q_DECLARE_ISRECORDTYPE_FOR_NDEF_RECORD() macros. The following example shows the class
declaration of the hypothetical \e {example.com:f} record type that encapsulates a single int
property foo.
\snippet nfc.cpp Specialized class definition
The developer only needs to provide implementations for the \c {foo()} and \c {setFoo()}
functions that parse and set the contents of the NDEF record's payload.
|
9305 |
- |
| qndefrecord.h |
|
2336 |
- |
| qndefrecord_p.h |
|
858 |
- |
| qnearfieldmanager.cpp |
!
\class QNearFieldManager
\brief The QNearFieldManager class provides access to notifications for NFC events.
\ingroup connectivity-nfc
\inmodule QtNfc
\since 5.2
NFC Forum devices support two modes of communications. The first mode, peer-to-peer
communications, is used to communicate between two NFC Forum devices. The second mode,
master/slave communications, is used to communicate between an NFC Forum device and an NFC
Forum Tag or Contactless Card. The targetDetected() signal is emitted when a target device
enters communications range. Communications can be initiated from the slot connected to this
signal.
NFC Forum devices generally operate as the master in master/slave communications. Some devices
are also capable of operating as the slave, so called Card Emulation mode. In this mode the
local NFC device emulates a NFC Forum Tag or Contactless Card.
Applications can connect to the targetDetected() and targetLost() signals to get notified when
an NFC Forum Tag enters or leaves proximity. Before these signals are emitted target detection
must be started with the startTargetDetection() function. Target detection can be stopped with
the stopTargetDetection() function. When the target is no longer required the target should be
deleted as other applications may be blocked from accessing the target.
\section1 NFC on Linux
The \l{https://github.com/linux-nfc/neard}{Linux NFC project} provides software to support NFC
on Linux platforms. The neard daemon will allow access to the supported hardware via DBus
interfaces. QtNfc requires neard version 0.14 which can be built from source or installed via
the appropriate Linux package manager. Not all API features are currently supported.
To allow QtNfc to access the DBus interfaces the neard daemon has to be running. In case of
problems debug output can be enabled by enabling categorized logging for 'qt.nfc.neard'.
|
10269 |
- |
| qnearfieldmanager.h |
|
1521 |
- |
| qnearfieldmanager_android.cpp |
env |
4250 |
- |
| qnearfieldmanager_android_p.h |
|
1835 |
- |
| qnearfieldmanager_generic.cpp |
Constructs a new near field manager private implementation.
|
522 |
- |
| qnearfieldmanager_generic_p.h |
|
729 |
- |
| qnearfieldmanager_ios.mm |
|
8067 |
- |
| qnearfieldmanager_ios_p.h |
|
2418 |
- |
| qnearfieldmanager_neard.cpp |
|
8666 |
- |
| qnearfieldmanager_neard_p.h |
|
1431 |
- |
| qnearfieldmanager_p.h |
|
1552 |
- |
| qnearfieldmanager_pcsc.cpp |
Constructs a new near field manager private implementation.
This object creates a worker thread with an instance of QPcscManager in
it. All the communication with QPcscManager is done using signal-slot
mechanism.
|
4757 |
- |
| qnearfieldmanager_pcsc_p.h |
|
1506 |
- |
| qnearfieldtarget.cpp |
!
\class QNearFieldTarget
\brief The QNearFieldTarget class provides an interface for communicating with a target
device.
\ingroup connectivity-nfc
\inmodule QtNfc
\since 5.2
QNearFieldTarget provides a generic interface for communicating with an NFC target device.
Both NFC Forum devices and NFC Forum Tag targets are supported by this class. All target
specific classes subclass this class.
The type() function can be used to get the type of the target device. The uid() function
returns the unique identifier of the target. The AccessMethods flags returns from the
accessMethods() function can be tested to determine which access methods are supported by the
target.
If the target supports NdefAccess, hasNdefMessage() can be called to test if the target has a
stored NDEF message, readNdefMessages() and writeNdefMessages() functions can be used to get
and set the NDEF message.
If the target supports TagTypeSpecificAccess, sendCommand() can be used to send a single
proprietary command to the target and retrieve the response.
|
12472 |
- |
| qnearfieldtarget.h |
|
3268 |
- |
| qnearfieldtarget_android.cpp |
|
16810 |
- |
| qnearfieldtarget_android_p.h |
|
2481 |
- |
| qnearfieldtarget_ios.mm |
|
16887 |
- |
| qnearfieldtarget_ios_p.h |
|
3205 |
- |
| qnearfieldtarget_neard_p.cpp |
|
13693 |
- |
| qnearfieldtarget_neard_p.h |
|
2271 |
- |
| qnearfieldtarget_p.cpp |
erasing |
3440 |
- |
| qnearfieldtarget_p.h |
|
2368 |
- |
| qnearfieldtarget_pcsc.cpp |
Construct QNearFieldTargetPrivateImpl instance.
This object communicates with a QPcscCard object that lives inside the
worker thread via signal-slot mechanism.
|
4033 |
- |
| qnearfieldtarget_pcsc_p.h |
|
2265 |
- |
| qtnfcglobal.h |
|
257 |
- |
| qtnfcglobal_p.h |
|
579 |
- |