TT_PATTERN_FILE_ADD(3)

💅 NAME 💅

tt_pattern_file_add — add a value to the file field of a pattern

okay bestie, quick vibe check: this is the library call page for tt_pattern_file_add, and we're folding that manual-name energy in right here. ✨

---

✨ SYNOPSIS ✨

       #include &<Tt/tt_c.h>
       Tt_status tt_pattern_file_add(
       Tt_pattern p,
       const char *file);

---

🦋 DESCRIPTION 🦋

So the tt_pattern_file_add function does exactly what it says on the label: it adds a value to the file field of the pattern you point at. 🎯

The application can use this call to set individual files on individual patterns. Cute, targeted, no chaos. 💖

The p argument is a unique handle for a message pattern. This handle is returned after tt_pattern_create(3) is called — that's where it comes from, bestie. 🫶

The file argument is the name of the file of the specified pattern. That's the file-name string going into the file field, periodt. 🎀

---

🎀 RETURN VALUE 🎀

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

---

🌸 APPLICATION USAGE 🌸

However — and this is the little caveat bestie — this call does not cause the pattern's ToolTalk session to be stored in the database. Nope, not doing that. 🙈

---

🔥 SEE ALSO 🔥

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

---

💖 that's the whole library-call page, bestie: source is the library-call corner of the manual, and no version or date got printed on it — so we're signing off with vibes only. 🎀✨