ONVIF:...esponse(3pm)

💖 ONVIF::Media::Elements::GetOSDsResponse 💖

okay bestie, welcome to the manual page for ONVIF::Media::Elements::GetOSDsResponse — yes the title's a whole mouthful, the manpage header lowkey truncates it to ONVIF:...esponse(3pm) but we know the truth 💅

---

🌸 NAME 🌸

ONVIF::Media::Elements::GetOSDsResponse — a whole Perl data type class, slaying as always ✨

---

🦋 DESCRIPTION 🦋

So basically? This is a Perl data type class for the XML Schema defined element GetOSDsResponse, and it lives in the namespace http://www.onvif.org/ver10/media/wsdl. That's it, that's the vibe. It's giving "I exist to represent one specific XML element" and honestly? Iconic. 👑

---

🎀 PROPERTIES 🎀

The following properties may be accessed using get_PROPERTY / set_PROPERTY methods — yes, the classic getter/setter duo, they never miss 🫶

• OSDs — the one and only property, and here's how you talk to it:

$element->set_OSDs($data);
$element->get_OSDs();

---

✨ METHODS ✨

💜 new

my $element = ONVIF::Media::Elements::GetOSDsResponse->new($data);

Constructor, bestie. It builds you a brand new element 🎀

The following data structure may be passed to new() — and no, we are not skipping a single line of it, because every nested hash down here matters:

{
  OSDs =>  { # ONVIF::Media::Types::OSDConfiguration
    VideoSourceConfigurationToken =>  { value => $some_value },
    Type => $some_value, # OSDType
    Position =>  { # ONVIF::Media::Types::OSDPosConfiguration
      Type =>  $some_value, # string
      Pos => ,
      Extension =>  { # ONVIF::Media::Types::OSDPosConfigurationExtension
      },
    },
    TextString =>  { # ONVIF::Media::Types::OSDTextConfiguration
      Type =>  $some_value, # string
      DateFormat =>  $some_value, # string
      TimeFormat =>  $some_value, # string
      FontSize =>  $some_value, # int
      FontColor =>  { # ONVIF::Media::Types::OSDColor
        Color => ,
      },
      BackgroundColor =>  { # ONVIF::Media::Types::OSDColor
        Color => ,
      },
      PlainText =>  $some_value, # string
      Extension =>  { # ONVIF::Media::Types::OSDTextConfigurationExtension
      },
    },
    Image =>  { # ONVIF::Media::Types::OSDImgConfiguration
      ImgPath =>  $some_value, # anyURI
      Extension =>  { # ONVIF::Media::Types::OSDImgConfigurationExtension
      },
    },
    Extension =>  { # ONVIF::Media::Types::OSDConfigurationExtension
    },
  },
},

Look at all those nested types. The way OSDConfiguration holds OSDPosConfiguration, OSDTextConfiguration, OSDImgConfiguration and OSDConfigurationExtension all at once? Multitasking queen 👑 The comments telling you which Perl type each block maps to are your besties here — OSDType, string, int, anyURI — respect them, they're literally labeled for you 🧚

---

🌈 AUTHOR 🌈

Generated by SOAP::WSDL — so no human hand-wrote this beauty, it was birthed by a code generator. Auto-generated and still serving looks 💅

---

and that's the whole page, bestie!! fr fr you now know everything this class has to offer 💖

this lil manual is from perl v5.40.1, dated 2026-02-01, and in the footer it goes by ONVIF:...esponse(3pm) — yeah the manpage system truncates it, we don't gatekeep, we just vibe 🦋✨