XMADDPROTOCOLS(3)
π NAME π
XmAddProtocols β a VendorShell function that adds the protocols to the protocol manager and allocates the internal tables π«Ά
okay so bestie, this is one of those library call pages, the kind you find in the X/Motif corner of the man world. she's not a command, she's a function, and she's here to do exactly two things and she does them fabulously. no cap. π
β¨ SYNOPSIS β¨
#include <Xm/Protocols.h>
void XmAddProtocols(
Widget shell,
Atom property,
Atom *protocols,
Cardinal num_protocols);
look at her. four arguments. clean. iconic. not a single default value in sight because this girl doesn't do defaults, she does exactly what you tell her. π
πΈ DESCRIPTION πΈ
XmAddProtocols adds the protocols to the protocol manager and allocates the internal tables. that's it. that's the whole vibe. she walks in, she registers your protocols, she allocates the internal tables, she leaves. main character energy fr fr. π
also, plot twist that you absolutely need to know:
XmAddWMProtocols is a convenience interface. it calls XmAddProtocols with the property value set to the atom returned by interning WM_PROTOCOLS. so likeβ¦ she's the same girl, just already dressed for the WM party. π
π¦ the parameters (yes queen, all four) π¦
shellβ specifies the widget with which the protocol property is associated πpropertyβ specifies the protocol property β¨protocolsβ specifies the protocolAtoms π§num_protocolsβ specifies the number of elements inprotocolsπ
π do not fumblenum_protocols, bestie. she wants the count of elements inprotocols. that is a number. that is your job. that is not a vibe check, that is a fact check.
and if you want the full tea on VendorShell and all her associated resources β like, the whole lore, not just the highlights β go read VendorShell(3). she's the source of truth and she's serving. π«Ά
π RELATED π
(the one that adds, the one that adds but with WM_PROTOCOLS already interned, the one that interns your atoms, and the one that takes it all back when you're done. a whole little friend group. obsessed. π)
aaaand that's the page!! π this was XmAddProtocols from the library call manual section β yes, the header and footer both just say XmAddProtocols(library call) like a signature she's not changing for anybody, periodt. go forth, add your protocols, allocate those internal tables, and slay responsibly. πβ¨π¦
π¦ where this page comes from
- alpine 3.24: motif-doc 2.5.2-r0 Β· LGPL-2.1-or-later
- arch rolling: openmotif 2.3.8-4 Β· LGPL-2.1-or-later
- centos-stream 9: motif-devel 2.3.4-32.el9 Β· LGPLv2+
- centos-stream 9: motif-devel 2.3.4-32.el9 Β· LGPLv2+
- epel 10: motif-devel 2.3.8-2.el10_2 Β· LicenseRef-Callaway-LGPLv2+
- fedora 43: motif-devel 2.3.8-1.fc43 Β· LicenseRef-Callaway-LGPLv2+
- fedora 43: motif-devel 2.3.8-1.fc43 Β· LicenseRef-Callaway-LGPLv2+
- fedora 43: motif-devel 2.3.8-2.fc43 Β· LicenseRef-Callaway-LGPLv2+
- fedora 43: motif-devel 2.3.8-2.fc43 Β· LicenseRef-Callaway-LGPLv2+
- fedora 44: motif-devel 2.3.8-3.fc44 Β· LicenseRef-Callaway-LGPLv2+
- fedora 44: motif-devel 2.3.8-3.fc44 Β· LicenseRef-Callaway-LGPLv2+
- nixos 26.05: motif 2.3.8
- nixpkgs unstable: motif 2.3.8
- opensuse-leap 16.0: motif-devel 2.3.8-bp160.1.1 Β· LGPL-2.1-or-later
- opensuse-leap 16.0: motif-devel 2.3.8-bp160.1.1 Β· LGPL-2.1-or-later
- opensuse-leap 16.0: motif-devel 2.3.8-bp160.1.1 Β· LGPL-2.1-or-later
- opensuse-leap 16.0: motif-devel 2.3.8-bp160.1.1 Β· LGPL-2.1-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms