ONVIF::...cOptions(3)

πŸ“¦ version 1.38.6, in nixpkgs unstable

πŸ’– ONVIF::...cOptions(3) πŸ’–

okay so bestie, welcome to ONVIF::...cOptions(3) β€” a page straight out of the User Contributed Perl Documentation collection. Pull up a chair, grab a lil snack πŸ“, and let's get into it.


✨ NAME ✨

ONVIF::PTZ::Types::JpegDecOptions β€” that's the whole name, no cap. That's our main character πŸ‘‘.


🌸 DESCRIPTION 🌸

So this is a Perl data type class for the XML Schema defined complexType JpegDecOptions, and it lives in the namespace http://www.onvif.org/ver10/schema. That's it, that's the vibe. It's giving "humble little type class that knows exactly what it is" πŸ’….


πŸŽ€ PROPERTIES πŸŽ€

The following properties may be accessed using get_PROPERTY / set_PROPERTY methods β€” yes bestie, that's the pattern, get and set, get and set, iconic behavior fr fr:

  • πŸ”₯ ResolutionsAvailable
  • πŸ”₯ SupportedInputBitrate
  • πŸ”₯ SupportedFrameRate

Three of them. Slay.


πŸ¦‹ METHODS πŸ¦‹

🌈 new

Constructor. The way this works is the following data structure may be passed to new() β€” copy it exactly, don't freestyle it, okay? 😭

 { # ONVIF::PTZ::Types::JpegDecOptions
   ResolutionsAvailable =>  { # ONVIF::PTZ::Types::VideoResolution
     Width =>  $some_value, # int
     Height =>  $some_value, # int
   },
   SupportedInputBitrate =>  { # ONVIF::PTZ::Types::IntRange
     Min =>  $some_value, # int
     Max =>  $some_value, # int
   },
   SupportedFrameRate =>  { # ONVIF::PTZ::Types::IntRange
     Min =>  $some_value, # int
     Max =>  $some_value, # int
   },
 },

Notice how ResolutionsAvailable is a ONVIF::PTZ::Types::VideoResolution with Width and Height (both int), while SupportedInputBitrate and SupportedFrameRate are both ONVIF::PTZ::Types::IntRange with a Min and a Max (both int too). The $some_value is literally the placeholder β€” you fill it in, bestie 🫢. And yes, those # int comments are the type hints, keep them.


πŸ’œ AUTHOR πŸ’œ

Generated by SOAP::WSDL. Not me, not you β€” the generator did it. Respect to the machine πŸ€–βœ¨.


πŸ’€ quick vibe check reminder: don't go renaming any of these properties or dropping a Min/Max, because the XML Schema is not gonna be flexible about it. Periodt.

okay that's the whole page, you ate that πŸ’… β€” this cutie was brought to you by perl v5.42.3, dated 1980-01-01, and yes the page answers to ONVIF::...cOptions(3) when you call it. mwah πŸ’–πŸŽ€πŸ¦‹

πŸ“¦ where this page comes from