TT_OTYPE_HSIG_OP(3)

💖 NAME 💖

tt_otype_hsig_op (library call) — okay so this is the ToolTalk function that returns the operation name of a request signature of an otype. Bestie, it's literally right there in the name. 💅✨

✨ SYNOPSIS ✨

#include &<Tt/tt_c.h>
char *tt_otype_hsig_op(
       const char *otype,
       int sig);

🦋 DESCRIPTION 🦋

Okay so tt_otype_hsig_op returns the operation name of the sigth request signature of the given otype. No cap.

The otype argument is the object type involved in this operation. The sig argument is the zero-based index into the request signatures of the given otype. Zero-based index means exactly what it sounds like, bestie — it's the index, and it starts at zero. 🫶

🔥 RETURN VALUE 🔥

Upon successful completion, the tt_otype_hsig_op function returns the operation attribute of the specified request signature. The application can use tt_ptr_error(3) to extract one of the following Tt_status values from the returned pointer:

• 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_NUM — the integer value passed was invalid (out of range). 🚫
• TT_ERR_OTYPE — the specified object type is not the name of an installed object type. 💀

🎀 APPLICATION USAGE 🎀

The application should use tt_free(3) to free any data stored in the address returned by the ToolTalk API. Clean up after yourself, bestie — it's giving responsible main character energy. 🧚💖

🌈 SEE ALSO 🌈

• Tt/tt_c.h - Tttt_c(5)
• tt_otype_hsig_arg_type(3)
• tt_otype_hsig_arg_mode(3)
• tt_otype_hsig_args_count(3)
• tt_otype_hsig_count(3)
• tt_ptr_error(3)
• tt_free(3)

---

Sign-off: tt_otype_hsig_op(library call) — that's the footer vibe, and there's no separate source/version/date line attached on this page. Periodt. 💅🎀✨