AttributeIdLookupGetName(ServiceAttributeId, Type, LanguageBaseItem, LanguageBaseItem) Method
Retrieves the name of the SDP Attribute ID with the given value
and using one of the languages from the supplied LanguageBaseItem
in the specified AttributeID class sets.
Namespace: InTheHand.Net.Bluetooth.AttributeIdsAssembly: InTheHand.Net.Bluetooth (in InTheHand.Net.Bluetooth.dll) Version: 4.0.32+5cdf1cfd21064ea31c5de33d160200ca1c4bc218
public static string GetName(
ServiceAttributeId id,
Type[] attributeIdDefiningClasses,
LanguageBaseItem[] langBaseList,
out LanguageBaseItem applicableLangBase
)
Public Shared Function GetName (
id As ServiceAttributeId,
attributeIdDefiningClasses As Type(),
langBaseList As LanguageBaseItem(),
<OutAttribute> ByRef applicableLangBase As LanguageBaseItem
) As String
public:
static String^ GetName(
ServiceAttributeId id,
array<Type^>^ attributeIdDefiningClasses,
array<LanguageBaseItem^>^ langBaseList,
[OutAttribute] LanguageBaseItem^% applicableLangBase
)
static member GetName :
id : ServiceAttributeId *
attributeIdDefiningClasses : Type[] *
langBaseList : LanguageBaseItem[] *
applicableLangBase : LanguageBaseItem byref -> string
- id ServiceAttributeId
-
The Attribute Id as an ServiceAttributeId
- attributeIdDefiningClasses Type
-
The set of classes defining Attribute IDs for the service classed contained
in the record containing this attribute id.
- langBaseList LanguageBaseItem
-
The list of LanguageBaseItem applying
to the current record. They are used when an attribute is marked as a
multi-language one and thus need the base offset removed from the specified
numerical value.
- applicableLangBase LanguageBaseItem
-
The applicable LanguageBaseItem if the
matched attribute is a multi-language one.
( in Visual Basic), if no attribute was matched
or it was not a multi-language one.
String
A string containing the name of the Attribute ID whose numerical value is
id,
or a null reference (
Nothing in Visual Basic) if no such constant is found.
Each particular service (ObexPushProfile, SerialPortProfile) etc defines
its own SDP record content and the Attribute IDs are defined locally in
each, and thus with values overlapping with other service specifications.
Therefore for each profile we must define the set of Attribute IDs used, this
is done by creating a class for each with the IDs defined as const
member fields.