Uses of Class
org.bluez.datatypes.TwoTuple
Packages that use TwoTuple
-
Uses of TwoTuple in org.bluez
Modifier and TypeMethodDescriptionTwoTuple<org.freedesktop.dbus.FileDescriptor, org.freedesktop.dbus.types.UInt16> GattCharacteristic1.AcquireNotify(Map<String, org.freedesktop.dbus.types.Variant<?>> _options) From bluez documentation:
Acquire file descriptor and MTU for notify.TwoTuple<org.freedesktop.dbus.FileDescriptor, org.freedesktop.dbus.types.UInt16> GattCharacteristic1.AcquireWrite(Map<String, org.freedesktop.dbus.types.Variant<?>> _options) From bluez documentation:
Acquire file descriptor and MTU for writing.TwoTuple<org.freedesktop.dbus.DBusPath,Properties>[] From bluez documentation:
Return a list of items found
-
Uses of TwoTuple in org.bluez.mesh
Methods in org.bluez.mesh that return TwoTupleModifier and TypeMethodDescriptionTwoTuple<org.freedesktop.dbus.DBusPath, List<TwoTuple<Byte, List<TwoTuple<org.freedesktop.dbus.types.UInt16, Map<String, org.freedesktop.dbus.types.Variant<?>>>>>>> Network1.Attach(org.freedesktop.dbus.DBusPath _appRoot, org.freedesktop.dbus.types.UInt64 _token) From bluez documentation:
This is the first method that an application must call to get
access to mesh node functionalities.
The app_root parameter is a D-Bus object root path of
the application that implements org.bluez.mesh.Application1
interface.TwoTuple<org.freedesktop.dbus.types.UInt16, org.freedesktop.dbus.types.UInt16> Provisioner1.RequestProvData(byte _count) From bluez documentation:
This method is implemented by a Provisioner capable application
and is called when the remote device has been fully
authenticated and confirmed.
The count parameter is the number of consecutive unicast
addresses the remote device is requesting.
Return Parameters are from the Mesh Profile Spec:
net_index - Subnet index of the net_key
unicast - Primary Unicast address of the new node
Methods in org.bluez.mesh that return types with arguments of type TwoTupleModifier and TypeMethodDescriptionTwoTuple<org.freedesktop.dbus.DBusPath, List<TwoTuple<Byte, List<TwoTuple<org.freedesktop.dbus.types.UInt16, Map<String, org.freedesktop.dbus.types.Variant<?>>>>>>> Network1.Attach(org.freedesktop.dbus.DBusPath _appRoot, org.freedesktop.dbus.types.UInt64 _token) From bluez documentation:
This is the first method that an application must call to get
access to mesh node functionalities.
The app_root parameter is a D-Bus object root path of
the application that implements org.bluez.mesh.Application1
interface.TwoTuple<org.freedesktop.dbus.DBusPath, List<TwoTuple<Byte, List<TwoTuple<org.freedesktop.dbus.types.UInt16, Map<String, org.freedesktop.dbus.types.Variant<?>>>>>>> Network1.Attach(org.freedesktop.dbus.DBusPath _appRoot, org.freedesktop.dbus.types.UInt64 _token) From bluez documentation:
This is the first method that an application must call to get
access to mesh node functionalities.
The app_root parameter is a D-Bus object root path of
the application that implements org.bluez.mesh.Application1
interface. -
Uses of TwoTuple in org.bluez.obex
Methods in org.bluez.obex that return TwoTupleModifier and TypeMethodDescriptionObjectPush1.ExchangeBusinessCards(String _clientfile, String _targetfile) From bluez documentation:
Push the client's business card to the remote device
and then retrieve the remote business card and store
it in a local file.
If an empty target file is given, a name will be
automatically calculated for the temporary file.
The returned path represents the newly created transfer,
which should be used to find out if the content has been
successfully transferred or if the operation fails.
The properties of this transfer are also returned along
with the object path, to avoid a call to GetProperties.
From bluez documentation:
Download message and store it in the target file.
If an empty target file is given, a temporary file
will be automatically generated.
The returned path represents the newly created transfer,
which should be used to find out if the content has been
successfully transferred or if the operation fails.
The properties of this transfer are also returned along
with the object path, to avoid a call to GetProperties.
From bluez documentation:
Copy the source file (from remote device) to the
target file (on local filesystem).
If an empty target file is given, a name will be
automatically calculated for the temporary file.
The returned path represents the newly created transfer,
which should be used to find out if the content has been
successfully transferred or if the operation fails.
The properties of this transfer are also returned along
with the object path, to avoid a call to GetProperties.
Synchronization1.GetPhonebook(String _targetfile) From bluez documentation:
Retrieve an entire Phonebook Object store from remote
device, and stores it in a local file.
If an empty target file is given, a name will be
automatically calculated for the temporary file.
The returned path represents the newly created transfer,
which should be used to find out if the content has been
successfully transferred or if the operation fails.
The properties of this transfer are also returned along
with the object path, to avoid a call to GetProperties.
From bluez documentation:
Return an array of vcard-listing data where every entry
consists of a pair of strings containing the vcard
handle and the contact name.MessageAccess1.ListMessages(String _folder, Map<String, org.freedesktop.dbus.types.Variant<?>> _filter) From bluez documentation:
Returns an array containing the messages found in the
given subfolder of the current folder, or in the
current folder if folder is empty.
Possible Filters: Offset, MaxCount, SubjectLength, Fields,
Type, PeriodStart, PeriodEnd, Status, Recipient, Sender,
Priority
Each message is represented by an object path followed
by a dictionary of the properties.
Properties:
string Subject:
Message subject
string Timestamp:
Message timestamp
string Sender:
Message sender name
string SenderAddress:
Message sender address
string ReplyTo:
Message Reply-To address
string Recipient:
Message recipient name
string RecipientAddress:
Message recipient address
string Type:
Message type
Possible values: "email", "sms-gsm",
"sms-cdma" and "mms"
uint64 Size:
Message size in bytes
boolean Text:
Message text flag
Specifies whether message has textual
content or is binary only
string Status:
Message status
Possible values for received messages:
"complete", "fractioned", "notification"
Possible values for sent messages:
"delivery-success", "sending-success",
"delivery-failure", "sending-failure"
uint64 AttachmentSize:
Message overall attachment size in bytes
boolean Priority:
Message priority flag
boolean Read:
Message read flag
boolean Sent:
Message sent flag
boolean Protected:
Message protected flag
PhonebookAccess1.Pull(String _vcard, String _targetfile, Map<String, org.freedesktop.dbus.types.Variant<?>> _filters) From bluez documentation:
Given a vcard handle, retrieve the vcard in the current
phonebook object and store it in a local file.
If an empty target file is given, a name will be
automatically calculated for the temporary file.
The returned path represents the newly created transfer,
which should be used to find out if the content has been
successfully transferred or if the operation fails.
The properties of this transfer are also returned along
with the object path, to avoid a call to GetProperties.
Possbile filters: Format and Fields
PhonebookAccess1.PullAll(String _targetfile, Map<String, org.freedesktop.dbus.types.Variant<?>> _filters) From bluez documentation:
Return the entire phonebook object from the PSE server
in plain string with vcard format, and store it in
a local file.
If an empty target file is given, a name will be
automatically calculated for the temporary file.
The returned path represents the newly created transfer,
which should be used to find out if the content has been
successfully transferred or if the operation fails.
The properties of this transfer are also returned along
with the object path, to avoid a call to GetProperties.
Possible filters: Format, Order, Offset, MaxCount and
Fields
ObjectPush1.PullBusinessCard(String _targetfile) From bluez documentation:
Request the business card from a remote device and
store it in the local file.
If an empty target file is given, a name will be
automatically calculated for the temporary file.
The returned path represents the newly created transfer,
which should be used to find out if the content has been
successfully transferred or if the operation fails.
The properties of this transfer are also returned along
with the object path, to avoid a call to GetProperties.
MessageAccess1.PushMessage(String _sourcefile, String _folder, Map<String, org.freedesktop.dbus.types.Variant<?>> _args) From bluez documentation:
Transfer a message (in bMessage format) to the
remote device.
The message is transferred either to the given
subfolder of the current folder, or to the current
folder if folder is empty.
Possible args: Transparent, Retry, Charset
The returned path represents the newly created transfer,
which should be used to find out if the content has been
successfully transferred or if the operation fails.
The properties of this transfer are also returned along
with the object path, to avoid a call to GetAll.
From bluez documentation:
Copy the source file (from local filesystem) to the
target file (on remote device).
The returned path represents the newly created transfer,
which should be used to find out if the content has been
successfully transferred or if the operation fails.
The properties of this transfer are also returned along
with the object path, to avoid a call to GetProperties.
Synchronization1.PutPhonebook(String _sourcefile) From bluez documentation:
Send an entire Phonebook Object store to remote device.
The returned path represents the newly created transfer,
which should be used to find out if the content has been
successfully transferred or if the operation fails.
The properties of this transfer are also returned along
with the object path, to avoid a call to GetProperties.
PhonebookAccess1.Search(String _field, String _value, Map<String, org.freedesktop.dbus.types.Variant<?>> _filters) From bluez documentation:
Search for entries matching the given condition and
return an array of vcard-listing data where every entry
consists of a pair of strings containing the vcard
handle and the contact name.
vcard : name paired string match the search condition.
field : the field in the vcard to search with
{ "name" (default) | "number" | "sound" }
value : the string value to search for
Possible filters: Order, Offset and MaxCount
From bluez documentation:
Send one local file to the remote device.
The returned path represents the newly created transfer,
which should be used to find out if the content has been
successfully transferred or if the operation fails.
The properties of this transfer are also returned along
with the object path, to avoid a call to GetProperties.