TT_SPEC_BPROP_SET(3)

πŸ“¦
version 2.5.3 Β· 2 versions
, in nixos 26.05

πŸ’– tt_spec_bprop_set β€” library call πŸ’–

okay bestie, we’re in tt_spec_bprop_set territory: it’s a library call, it replaces a spec property’s current values with a fresh byte-string, and it’s honestly giving β€œclean slate, main character energy.” let’s go ✨


🌸 NAME 🌸

tt_spec_bprop_set β€” replace any current values stored under this spec property with a new byte-string.

✨ SYNOPSIS ✨

#include &<Tt/tt_c.h>
Tt_status tt_spec_bprop_set(
const char *objid,
const char *propname,
const unsigned char *value,
int length);

πŸ¦‹ DESCRIPTION πŸ¦‹

The tt_spec_bprop_set function replaces any current values stored under this spec property with a new byte-string. lowkey iconic, ngl.

The objid argument is the identifier of the object involved in this operation. The propname argument is the name of the property which stores the values. The value argument is the byte-string to be added to the property value list. If the value is NULL, the property is removed entirely. The length argument is the length of the value in bytes. fr fr, that’s the whole vibe check.

bestie PSA: NULL here is not β€œtiny empty value” β€” it means the property gets removed entirely. periodt πŸ’…

πŸ‘‘ RETURN VALUE πŸ‘‘

Upon successful completion, the tt_spec_bprop_set function returns the status of the operation as one of the following Tt_status values:

  • TT_OK β€” the operation completed successfully. slay.
  • TT_ERR_NOMP β€” the ttsession(1) process is not running and the ToolTalk service cannot restart it.
  • TT_ERR_OBJID β€” the objid passed to the ToolTalk service does not reference an existing object spec.
  • TT_ERR_PROPLEN β€” the specified property value is too long. (the maximum size is implementation specific, but is at least 64.)
  • TT_ERR_PROPNAME β€” the specified property name is syntactically invalid.

🌈 SEE ALSO 🌈


footer sign-off: tt_spec_bprop_set (library call) β€” that’s the manual-name energy, no date attached on this page, mwah πŸ’…πŸ’–βœ¨

πŸ“¦ where this page comes from