You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Diff between 20220114..20230405 added this, to which I have a comment:
+=== Named properties (0x8000 – 0xfffe)
+
+[NOTE]
+The actual meaning of these item types can be overwritten by the
+name-to-id map.
+
+[cols="1,1,1,5",options="header"]
+|===
+| Item type | Value type | Identifier | Description
+| 0x8001 | 0x000b (Boolean) | PR_EMS_AB_DISPLAY_NAME_OVERRIDE | [yellow-background]*Unknown*
+| | | |
The addressbook RPC interface (NSPI) does not have any calls for named property translation, in other words, there is no concept of named properties at all and 0x8000..0xFFFE are just regular tagged properties there.
The text was updated successfully, but these errors were encountered:
@jengelh thx for that context, I'll have a look when time permits. This are work in progress notes.
joachimmetz
changed the title
Do not consider PR_* as named properties
Documentation: clarify number properties in addressbook RPC interface
Apr 5, 2023
Diff between 20220114..20230405 added this, to which I have a comment:
The addressbook RPC interface (NSPI) does not have any calls for named property translation, in other words, there is no concept of named properties at all and 0x8000..0xFFFE are just regular tagged properties there.
The text was updated successfully, but these errors were encountered: