TT_MESSAGE_CLASS(3)

🎀 tt_message_class 🎀

okay so bestie, this one is from the library call manual — it's the tt_message_class page, and it's literally about grabbing the class attribute off a message. yes. 💅

✨ NAME ✨

tt_message_class — retrieve the class attribute from a message 🫶

🌸 SYNOPSIS 🌸

#include &<Tt/tt_c.h>
Tt_class tt_message_class(
Tt_message m);

💖 DESCRIPTION 💖

The tt_message_class function retrieves the class attribute from the specified message. That's the whole mission, no cap. ✨

The m argument is the opaque handle for the message involved in this operation. Keep it cute and keep it handy. 🫶

🔥 RETURN VALUE 🔥

Upon successful completion, the tt_message_class function returns a value that indicates whether the sender wants an action to take place after the message is received. The tt_message_class function returns one of the following Tt_status values:

• TT_NOTICE — a notice of an event. The sender does not want feedback on this message. lowkey just an FYI vibe 💅
• TT_REQUEST — a request for some action to be taken. The sender must be notified of progress, success or failure, and must receive any return values. highkey needs the receipts 🔥

The application can use tt_int_error(3) to extract one of the following Tt_status values from the Tt_class integer:

• 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_int_error(3)

---

okay bye bestie — that's tt_message_class from the library call manual, and the footer has no extra date/version line beyond that manual label, so mwah 💖🎀🦋