TT_PATTERN_USER_SET(3)

💖 tt_pattern_user_set 💖

okay so this is the library call page for tt_pattern_user_set, and she is lowkey iconic. bestie, we are storing info in the user data cells of a pattern object. no cap, that’s the whole vibe check.

🎀 NAME 🎀

tt_pattern_user_set — store information in the user data cells of a pattern object. periodt. 💅

✨ SYNOPSIS ✨

#include &<Tt/tt_c.h>
Tt_status tt_pattern_user_set(
Tt_pattern p,
int key,
void *v);

🦋 DESCRIPTION 🦋

The tt_pattern_user_set function stores information in the user data cells associated with the specified pattern object. main character energy, honestly.

The p argument is a unique handle for a message pattern. This handle is returned after tt_pattern_create(3) is called. The key argument is the specified user data cell. The value for each data cell must be unique for this pattern — not me being dramatic, it’s literally the rule. The v argument is the data cell, a piece of arbitrary user data that can hold a void *.

bestie, that uniqueness rule is real: the value for each data cell must be unique for this pattern. no duplicate-cell shenanigans. 🫶

💅 RETURN VALUE 💅

Upon successful completion, tt_pattern_user_set 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_POINTER — the pointer passed does not point to an object of the correct type for this operation. 💀

🌈 SEE ALSO 🌈

• Tt/tt_c.h - Tttt_c(5), tt_pattern_user(3), tt_pattern_create(3).

---

xoxo 💋 — this has been tt_pattern_user_set, a library call original. The footer didn’t come with a source/version/date stamp to hype up, so consider this the sparkly sign-off instead. 🫶