BRLAPI_PARAMVALUEPACKET_T(3)

πŸ“¦
version 6.9.1 Β· 6 versions
, in centos-stream 10, fedora 43, fedora 44, opensuse-leap 16.0, ubuntu resolute, ubuntu stonking

🌸 NAME 🌸

brlapi_paramValuePacket_t β€” bestie, this is a whole struct, and it's the one that carries parameter values (and updates) around in BrlAPI. It lives in the Library Functions Manual, so you know it's iconic. πŸ’…


✨ SYNOPSIS ✨

#include <brlapi_protocol.h>

πŸŽ€ Data Fields πŸŽ€

  • uint32_t flags
  • brlapi_param_t param
  • uint32_t subparam_hi
  • uint32_t subparam_lo
  • unsigned char data [BRLAPI_MAXPARAMSIZE]

πŸ’– Detailed Description πŸ’–

okay so literally, it's giving structure of Parameter value or update. That's the whole vibe. It's the little container that says "here's a value" or "here's an update" and then hands you the goods. 🫢


πŸ¦‹ Field Documentation πŸ¦‹

πŸ’œ unsigned char brlapi_paramValuePacket_t::data[BRLAPI_MAXPARAMSIZE]

Which sub-parameter being transmitted, lo 32bits ✨

🌸 uint32_t brlapi_paramValuePacket_t::flags

(no description given in the source, bestie β€” it's just sitting there, mysterious, main character energy πŸŽ€)

πŸ’… brlapi_param_t brlapi_paramValuePacket_t::param

Flags to tell how value was gotten πŸ‘‘

⭐ uint32_t brlapi_paramValuePacket_t::subparam_hi

Which parameter being transmitted 🌈

πŸ“ uint32_t brlapi_paramValuePacket_t::subparam_lo

Which sub-parameter being transmitted, hi 32bits πŸ’–

not me noticing the descriptions are doing their own little shuffle πŸ™ˆ β€” I'm just reporting them exactly as written, no cap, no edits, no "fixing." fr fr.

🌟 Author 🌟

Generated automatically by Doxygen for BrlAPI from the source code. (Doxygen said "I got this" and honestly? it ate. πŸ’€βœ¨)


and that's the whole page, bestie 🫢 this was BrlAPI Version 0.8, signing off from the Library Functions Manual β€” slay, bye πŸ’…πŸŽ€

πŸ“¦ where this page comes from