ONVIF::...jectTree(3)

💅 NAME 💅

ok so bestie, this is the perl doc page for ONVIF::Media::Types::ObjectTree — and yeah, the manual page name got truncated all cute and mysterious as ONVIF::...jectTree(3), but it's literally just the ObjectTree page, iykyk. ✨

---

🦋 DESCRIPTION 🦋

It's a Perl data type class, no cap. Specifically, it's the class for the XML Schema defined complexType ObjectTree, and it lives in the namespace http://www.onvif.org/ver10/schema. That's it, that's the whole vibe. 🎀

🌸 PROPERTIES 🌸

ok so these are the properties, and the way you touch them is via get_PROPERTY / set_PROPERTY methods — like get_Rename, set_Rename, you get it. The full lineup:

• Rename
• Split
• Merge
• Delete
• Extension

periodt. that's the list, all five of them, nothing skipped. 👑

---

✨ METHODS ✨

🧚 new 🧚

it's the constructor, bestie. and here's the data structure you may pass to new() — copying this exactly because details matter:

 { # ONVIF::Media::Types::ObjectTree
   Rename =>  { # ONVIF::Media::Types::Rename
     from => ,
     to => ,
   },
   Split =>  { # ONVIF::Media::Types::Split
     from => ,
     to => ,
   },
   Merge =>  { # ONVIF::Media::Types::Merge
     from => ,
     to => ,
   },
   Delete => ,
   Extension =>  { # ONVIF::Media::Types::ObjectTreeExtension
   },
 },

lowkey iconic how Rename, Split, and Merge all got that matching from / to glow-up, while Delete is just... Delete. main character energy honestly. and Extension is its own little ONVIF::Media::Types::ObjectTreeExtension situation. 🫶

ngl, notice how those from and to values have nothing after them in the source — that's exactly how it's written, so don't come for me, I'm just the messenger. 🙈

---

🌈 AUTHOR 🌈

Generated by SOAP::WSDL — not me, not you, the code did it. 💀

---

and that's a wrap, bestie!! 💖 this lil gem comes to you courtesy of perl v5.42.3 and is dated 1980-01-01 (yes, that date is real, we love a retro timestamp) — signing off, go forth and ObjectTree responsibly, mwah 🍓💜