XMTRANSFERSTARTREQUEST(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

πŸ’– XmTransferStartRequest πŸ’–

okay bestie, so this is the tea on XmTransferStartRequest β€” it's a library call from the X toolkit, and it's the little sparkly button that begins a MULTIPLE transfer ✨


🌸 NAME 🌸

XmTransferStartRequest β€” a toolkit function that begins a MULTIPLE transfer 🫢


✨ SYNOPSIS ✨

#include <Xm/Transfer.h>

void XmTransferStartRequest(
XtPointer transfer_id);

πŸ’… DESCRIPTION πŸ’…

so like, XmTransferStartRequest kicks off a MULTIPLE request, periodt. that MULTIPLE request can hold one or more calls to XmTransferValue β€” no cap, as many as you need 🌈

and then, when you're done flexing, your application concludes the whole MULTIPLE request by calling XmTransferSendRequest πŸ’«

ngl, XmTransferStartRequest is typically called by a destination callback or by a transfer procedure. iykyk.

  • transfer_id β€” Specifies a unique identifier for the data transfer operation. bestie, you should use the transfer_id passed in the XmDestinationCallbackStruct or XmSelectionCallbackStruct πŸ‘‘


and that's the whole vibe, bestie πŸ’– this was your girl, signing off from the XmTransferStartRequest(library call) page β€” literally iconic, obsessed, mwah πŸŽ€πŸ¦‹πŸ’œ