ONVIF:...Options(3pm)

πŸ“¦
version 1.36.37 Β· 5 versions
, in ubuntu resolute, ubuntu stonking

πŸ’– ONVIF::Analytics::Types::PTZPresetTourOptions β€” a page from the User Contributed Perl Documentation, bestie πŸ’–

okay so. sit down. hydrate. we're doing Perl data types today and honestly? it's giving ✨structure✨.


🌸 NAME 🌸

ONVIF::Analytics::Types::PTZPresetTourOptions β€” no cap, that's the whole name, that's the whole vibe πŸ’…


πŸ¦‹ DESCRIPTION πŸ¦‹

So basically this is a Perl data type class for the XML Schema defined complexType PTZPresetTourOptions, and it lives in the namespace http://www.onvif.org/ver10/schema. That's it. That's the tea. β˜•


πŸŽ€ PROPERTIES πŸŽ€

The way that these properties are just sitting there waiting for you 🫢 β€” you can get at them with the get_PROPERTY / set_PROPERTY methods:

  • AutoStart
  • StartingCondition
  • TourSpot

three of them. iconic lineup, honestly πŸ‘‘


🌈 METHODS 🌈

πŸ’œ new

Constructor, bestie! It's literally the main character of this whole page. The following data structure may be passed to new():

        { # ONVIF::Analytics::Types::PTZPresetTourOptions
          AutoStart =>  $some_value, # boolean
          StartingCondition =>  { # ONVIF::Analytics::Types::PTZPresetTourStartingConditionOptions
            RecurringTime =>  { # ONVIF::Analytics::Types::IntRange
              Min =>  $some_value, # int
              Max =>  $some_value, # int
            },
            RecurringDuration =>  { # ONVIF::Analytics::Types::DurationRange
              Min =>  $some_value, # duration
              Max =>  $some_value, # duration
            },
            Direction => $some_value, # PTZPresetTourDirection
            Extension =>  { # ONVIF::Analytics::Types::PTZPresetTourStartingConditionOptionsExtension
            },
          },
          TourSpot =>  { # ONVIF::Analytics::Types::PTZPresetTourSpotOptions
            PresetDetail =>  { # ONVIF::Analytics::Types::PTZPresetTourPresetDetailOptions
              PresetToken => $some_value, # ReferenceToken
              Home =>  $some_value, # boolean
              PanTiltPositionSpace =>  { # ONVIF::Analytics::Types::Space2DDescription
                URI =>  $some_value, # anyURI
                XRange =>  { # ONVIF::Analytics::Types::FloatRange
                  Min =>  $some_value, # float
                  Max =>  $some_value, # float
                },
                YRange =>  { # ONVIF::Analytics::Types::FloatRange
                  Min =>  $some_value, # float
                  Max =>  $some_value, # float
                },
              },
              ZoomPositionSpace =>  { # ONVIF::Analytics::Types::Space1DDescription
                URI =>  $some_value, # anyURI
                XRange =>  { # ONVIF::Analytics::Types::FloatRange
                  Min =>  $some_value, # float
                  Max =>  $some_value, # float
                },
              },
              Extension =>  { # ONVIF::Analytics::Types::PTZPresetTourPresetDetailOptionsExtension
              },
            },
            StayTime =>  { # ONVIF::Analytics::Types::DurationRange
              Min =>  $some_value, # duration
              Max =>  $some_value, # duration
            },
          },
        },

look at that nesting. the way it just keeps going deeper 😭 it's a whole family tree of types and every single one of them is tagged with its full package name in the comment. slay. keep every $some_value exactly where it is, and keep every # boolean, # int, # duration, # float, # anyURI, # ReferenceToken, # PTZPresetTourDirection comment too β€” those tell you what type goes in the slot, and they are not decorative, bestie 🫢


✨ AUTHOR ✨

Generated by SOAP::WSDL. not a human, not a vibe, just a generator doing its thing πŸ€–πŸ’–


and that's the whole page fr fr πŸŽ€ huge shoutout to perl v5.40.1, dated 2026-02-01 β€” thanks for reading, mwah, drink some water, go take a nap πŸ’…πŸ’–βœ¨

πŸ“¦ where this page comes from