TT_MESSAGE_CREATE_SUPER(3)

📦
version 2.5.3 · 2 versions
, in nixos 26.05

💅 tt_message_create_super 💅

okay bestie, this is the library call manual page for tt_message_create_super — and yes, the name is a whole mouthful, but we move. ✨

🎀 NAME 🎀

tt_message_create_super — create and re-address a copy of a message. periodt.

🌸 SYNOPSIS 🌸

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

🦋 DESCRIPTION 🦋

so real talk, tt_message_create_super creates a copy of the specified message and re-addresses the copy of the message to the parent of the otype contained within the message. no cap, that's the whole assignment. 💫

the m argument is the opaque handle for the message involved in this operation.

👑 RETURN VALUE 👑

upon successful completion, tt_message_create_super returns the opaque unique handle for the re-addressed message. the application can use tt_ptr_error(3) to extract one of the following Tt_status values from the returned handle:

  • TT_OK — the operation completed successfully. slay.
  • TT_ERR_ADDRESS — the specified Tt_address is invalid.
  • 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_OTYPE — the specified object type is not the name of an installed object type.
  • TT_ERR_POINTER — the pointer passed does not point to an object of the correct type for this operation.

🧚 APPLICATION USAGE 🧚

the otype of the message m can be determined using the tt_message_otype(3) function. iykyk.

🌈 SEE ALSO 🌈

and that's the page, bestie — cute sign-off time: the footer has no separate source/version or date line, it's just the library call title/manual name again, so we're closing the group chat with that exact energy. 💖🎀✨

📦 where this page comes from