XMTRANSFERSENDREQUEST(3)

πŸ“¦
version 2.5.2 Β· 2 versions
, in alpine 3.24, arch rolling, centos-stream 9, epel 10, fedora 43, fedora 44, nixos 26.05, nixpkgs unstable, opensuse-leap 16.0

πŸ’… XmTransferSendRequest β€” the library call manual page, bestie

okay so welcome to the XmTransferSendRequest(library call) page, you're gonna eat this up, it's short and sweet and honestly iconic ✨


🌸 NAME 🌸

XmTransferSendRequest β€” a toolkit function that transfers a MULTIPLE request 🫢


πŸŽ€ SYNOPSIS πŸŽ€

#include <Xm/Transfer.h>

void XmTransferSendRequest(
        XtPointer transfer_id,
        Time time);

πŸ¦‹ DESCRIPTION πŸ¦‹

so like, XmTransferSendRequest marks the end of a MULTIPLE request that was started by XmTransferStartRequest. that's it, that's the whole vibe. it's giving "closing the loop" energy πŸ’–

  • transfer_id β€” specifies a unique indentifier for the data transfer operation. lowkey important, it's how the whole thing knows which transfer we're talking about πŸ‘‘
  • time β€” specifies the time of the XEvent that triggered the data transfer. you should typically set this field to XtLastTimestampProcessed. fr fr, that's the move, don't overthink it πŸ’…

go read those too bestie, they're the rest of the transfer-request friend group 🧚


no cap, this is the XmTransferSendRequest(library call) page from the Xm library call manual, and that's the whole entire thing. periodt. πŸ’œ ✨ πŸ“

okay bye ily, that's the XmTransferSendRequest(library call) manual, dated however old it is and sourced from the library call pages, mwah πŸ˜­πŸ’–