XkbAllocGeomPoints(3)

πŸ’– NAME πŸ’–

okay so bestie, this is XkbAllocGeomPoints(3) from the XKB FUNCTIONS manual: XkbAllocGeomPoints β€” allocate points in an outline. slay.

✨ SYNOPSIS ✨

Status XkbAllocGeomPoints (XkbOutlinePtr outline, int num_needed);

πŸŽ€ ARGUMENTS πŸŽ€

  • outline β€” the outline where the points should be allocated, bestie. this is the one getting the new point space.
  • num_needed β€” the number of new points required. literally how many new points you need.

πŸ¦‹ DESCRIPTION πŸ¦‹

Okay so context: Xkb provides a number of functions to allocate and free subcomponents of a keyboard geometry. Use these functions to create or modify keyboard geometries. Major vibe check though: 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. no cap.

Also heads up: 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. so dramatic 😭.

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.

XkbAllocGeomPoints allocates space for num_needed points in the specified outline. The points are not initialized. it's giving "reserved seats but nobody sat down yet" ✨.

πŸ’… DIAGNOSTICS πŸ’…

  • BadAlloc β€” unable to allocate storage. storage said no πŸ’€
  • BadValue β€” an argument is out of range. one of the args is acting out of pocket πŸ™ˆ

that's the whole page, bestie 🫢 footer energy: X Version 11, libX11 1.8.14, and the XkbAllocGeomPoints(3) tag. mwah πŸ’‹

πŸ“¦ where this page comes from