Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Documentation: clarify number properties in addressbook RPC interface #3

Open
jengelh opened this issue Apr 5, 2023 · 1 comment
Open

Comments

@jengelh
Copy link

jengelh commented Apr 5, 2023

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.

@joachimmetz
Copy link
Member

@jengelh thx for that context, I'll have a look when time permits. This are work in progress notes.

@joachimmetz joachimmetz changed the title Do not consider PR_* as named properties Documentation: clarify number properties in addressbook RPC interface Apr 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants