TT_MESSAGE_CONTEXT_IVAL(3)

📦
version 2.5.3 · 2 versions
, in nixos 26.05

💖 NAME 💖

okay so this page is tt_message_context_ival from the library call manual, and it’s literally the function for retrieving the integer value of a message’s context, bestie 💅

🦋 SYNOPSIS 🦋

#include &<Tt/tt_c.h>
Tt_status tt_message_context_ival(
Tt_message m,
const char *slotname,
int *value);

✨ DESCRIPTION ✨

The tt_message_context_ival function retrieves the integer value of a message’s context. no cap, that’s the whole mission 🫶

The m argument is the opaque handle for the message involved in this operation. main character message energy, honestly 👑

The slotname argument describes the context of this message. The value argument points to the location to return the value. very “put the value right there” of it 💅

if there’s no context slot associated with slotname, tt_message_context_ival returns a NULL pointer in *value — that’s the documented move, so don’t be surprised, bestie 😭

🔥 RETURN VALUE 🔥

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

  • TT_OK — the operation completed successfully. ✅
  • TT_ERR_NOMP — the ttsession(1) process is not running and the ToolTalk service cannot restart it. 💀
  • TT_ERR_NUM — the integer value passed was invalid (out of range). 🚫
  • TT_ERR_POINTER — the pointer passed does not point to an object of the correct type for this operation. 🙈
  • TT_ERR_SLOTNAME — the specified slotname is syntactically invalid. 😬
  • TT_WRN_NOTFOUND — the named context does not exist on the specified message. 🔍

🌸 APPLICATION USAGE 🌸

The application can use tt_free(3) to free any data stored in the address returned by the ToolTalk API. clean up after yourself, icon behavior 🧚

🎀 SEE ALSO 🎀

footer/source-version vibes: tt_message_context_ival(library call) — and date? not printed on this page, so I’m not making one up, bestie 😭💖

📦 where this page comes from