video_displaydescr(3)

πŸ“¦
version 0.7.1 Β· 2 versions
, in nixos 26.05

🌈 NAME 🌈

okay bestie, <pink>video_displaydescr</pink> is the function that retrieves a byte block and a hash for identifying a specific display. it's giving β€œmonitor identity crisis? not on my watch” energy πŸ’… β€” and yes, we're in the <hotpink>Arcan Lua API</hotpink> house, manual page <pink>video_displaydescr(3)</pink> 🫢


✨ SYNOPSIS ✨

string:block, string:hash, table:metadata
video_displaydescr( int:dispid )

πŸŽ€ DESCRIPTION πŸŽ€

okay so picture this: you're dealing with multiple-monitors, and you need to track settings, calibration, and other monitor-individual properties. for that you need some kind of identity token, and that's literally what this function hands you. πŸ”₯

it returns the platform identity one, which for most cases should be an EDID formatted binary blob β€” along with a hash value of the contents of the block, for when user-readable names are not needed but a (hopefully) unique identifier is. no cap, that's the whole vibe 😌

and if the platform is capable of parsing the block, higher-level information may be available via the returned <cyan>metadata</cyan> table. these are display, platform, and OS dependent, bestie. possible keys include:

  • 'error'
  • 'make'
  • 'model'
  • 'serial'

that's it, that's the metadata menu 🌸


πŸ”₯ EXAMPLE πŸ”₯

function video_displaydescr0()
      warning( video_displaydescr(0) );
end

πŸ‘€ SEE ALSO πŸ‘€

  • <purple>vidsys</purple> β€” go check it out, bestie πŸ’œ

mwah πŸ’‹ β€” this cutie comes from the <purple>vidsys</purple> source/version, dated <purple>October 2026</purple>, and it's the <pink>video_displaydescr(3)</pink> manual page. slay, bye 🫢✨

πŸ“¦ where this page comes from