propertymap_struct(3)

💖 NAME 💖

okay so bestie, welcome to the propertymap_struct(3) page — it’s from the Library Functions Manual, and the NAME section is literally just propertymap_struct. That’s it. Iconic minimalism, no cap. 💅

🌸 SYNOPSIS 🌸

✨ Data Fields ✨

• char * description — the char * field, bestie. Its field doc is down below, keep scrolling. 🫶
• LIBMTP_property_t id — typed exactly as LIBMTP_property_t.
• uint16_t ptp_id — typed exactly as uint16_t.
• struct propertymap_struct * next — typed exactly as struct propertymap_struct * next.

🎀 Field Documentation 🎀

okay so here’s where the original gets into the field docs. lowkey important: next does not get its own field-doc subsection in the original — it just hangs out in Data Fields with main character energy but no paragraph. 🙈

💜 char* propertymap_struct::description 💜

The field doc says: Text description for the property. It’s also Referenced by LIBMTP_Get_Property_Description(). That’s the whole vibe — description is the text-y one, periodt. ✨

🦋 LIBMTP_property_t propertymap_struct::id 🦋

The doc for id is: LIBMTP internal type for the property. And yeah, it’s Referenced by LIBMTP_Get_Property_Description() too. So both description and id are linked to that same function, fr fr. 🫶

🌈 uint16_t propertymap_struct::ptp_id 🌈

ptp_id is typed uint16_t, and its field doc is exactly: PTP ID for the property. short, sweet, slaying. 🍓

👑 Author 👑

The Author section literally says: Generated automatically by Doxygen for libmtp from the source code. So the author is not a human bestie — it’s Doxygen doing its little robot thing for libmtp. 🤖💖

cute sign-off time, bestie: footer source/version vibes are libmtp, Version 1.1.23, and it’s the propertymap_struct(3) page. The original footer doesn’t list a date, so I’m not inventing one — accuracy is the vibe. 💜✨