XkbAllocGeomDoodads(3)

💖 XkbAllocGeomDoodads 💖

okay bestie, this icon is from the XKB FUNCTIONS manual, and she's here to make room for doodads in your keyboard geometry. It's giving "reserve the space, then fill in the details yourself" energy 💅✨

---

💖 NAME 💖

XkbAllocGeomDoodads — allocate doodads that are global to a keyboard geometry. Periodt.

✨ SYNOPSIS ✨

Status XkbAllocGeomDoodads (XkbGeometryPtr geom, int num_needed);

🎀 ARGUMENTS 🎀

• geom — the geometry for which doodads should be allocated, bestie.
• num_needed — the number of new doodads required. Like, count them. 🔢

🦋 DESCRIPTION 🦋

okay so Xkb provides a number of functions to allocate and free subcomponents of a keyboard geometry. Use these functions to create or modify keyboard geometries. 🛠️

Vibe check: these functions merely allocate space for the new element(s), and it is up to you to fill in the values explicitly in your code. They are not doing the whole glow-up for you, bestie. 💅

These allocation functions increase sz_* but never touch num_* — unless there is an allocation failure, in which case they reset both sz_* and num_* to zero. 😭

These functions return Success if they succeed, BadAlloc if they are not able to allocate space, or BadValue if a parameter is not as expected.

XkbAllocGeomDoodads allocates num_needed doodads and adds them to the specified geometry geom. No initialization of the doodads is done. So they show up with zero styling — you have to dress them yourself. 🎀

💅 DIAGNOSTICS 💅

• BadAlloc — unable to allocate storage. The allocation said "not today" 💀
• BadValue — an argument is out of range. One of your params is giving "off the map" energy 🙈

---

xoxo, this page is serving X Version 11 / libX11 1.8.14 energy, and the footer didn't give me a date so I'm not inventing one — stay iconic, bestie 💖✨