structar(3)

💖 NAME 💖

okay so bestie, this is structar(3) from the Library Functions Manual, and it's literally the libmtp data structures page. The NAME is structar - libmtp data structures — no cap, that's the whole vibe. It's giving "here are the structs, drink water, read the types." 💅

✨ SYNOPSIS ✨

🎀 Data Structures

• struct LIBMTP_device_entry_struct
• struct LIBMTP_raw_device_struct
• struct LIBMTP_error_struct
• struct LIBMTP_allowed_values_struct
• struct LIBMTP_device_extension_struct
• struct LIBMTP_mtpdevice_struct
• struct LIBMTP_file_struct
• struct LIBMTP_track_struct
• struct LIBMTP_playlist_struct
• struct LIBMTP_album_struct
• struct LIBMTP_folder_struct
• struct LIBMTP_filesampledata_struct
• struct LIBMTP_devicestorage_struct

🧚 Typedefs

• typedef enum LIBMTP_event_enum LIBMTP_event_t

🌈 Enumerations

Here's the enum, copied exactly because we do not play with types:

       enum LIBMTP_event_enum { LIBMTP_EVENT_NONE, LIBMTP_EVENT_STORE_ADDED,
           LIBMTP_EVENT_STORE_REMOVED, LIBMTP_EVENT_OBJECT_ADDED,
           LIBMTP_EVENT_OBJECT_REMOVED, LIBMTP_EVENT_DEVICE_PROPERTY_CHANGED }

🌸 Detailed Description 🌸

So this heading is here, and the original page has... no body text under it. It's just standing there, mysterious, main character energy. 💀 We move on.

🦋 Enumeration Type Documentation 🦋

enum LIBMTP_event_enum

This one is described as LIBMTP Event structure TODO: add all externally visible events here — yes, that's the exact note, TODO and all. 🙈 So the docs are lowkey asking for all externally visible events to be added here. Noted, bestie.

👑 Author 👑

Generated automatically by Doxygen for libmtp from the source code. So Doxygen did its thing and spat this out automatically. Slay, I guess. ✨

Cute little sign-off: this page comes from libmtp, Version 1.1.23, and its header/footer identifies it as structar(3). The original footer didn't include a date, so we're not inventing one — no fake timestamp, periodt. 💜🫶