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

πŸ’… NAME πŸ’…

XmDropSiteConfigureStackingOrder β€” a Drag and Drop function that reorders a stack of widgets that are registered drop sites ✨

(this one lives in the library call manual, bestie β€” XmDropSiteC...ackingOrder, you know the one 🫢)


πŸŽ€ SYNOPSIS πŸŽ€

#include <Xm/DragDrop.h>
void XmDropSiteConfigureStackingOrder(
Widget widget,
Widget sibling,
Cardinal stack_mode);

πŸ¦‹ DESCRIPTION πŸ¦‹

okay so XmDropSiteConfigureStackingOrder changes the stacking order of the drop site specified by widget. πŸ’«

and like… why do we care? because the stacking order is literally what controls the manner in which drag-under effects are clipped by overlapping siblings, regardless of whether they are active. yes, even the inactive ones. the audacity, honestly 😭

the stack mode is relative either to the entire stack, or to another drop site within the stack β€” dealer's choice.

⚠️ but bestie, hear me: the stack order can be modified only if the drop sites are siblings in both the widget and drop site hierarchy, and the widget parent of the drop sites is registered as a composite drop site. no siblings, no composite parent, no restacking. periodt. πŸ’€
  • widget β€” specifies the drop site to be restacked. that's the one getting its glow-up ✨
  • sibling β€” specifies a sibling drop site for stacking operations. if you specify it, then widget is restacked relative to this drop site's stack position. it's giving "you're standing next to your friend now" energy 🫢
  • stack_mode β€” specifies the new stack position for the specified widget. the values are XmABOVE and XmBELOW. here's the tea πŸ“

if a sibling is specified, then widget is restacked like this:

  • XmABOVE β€” the widget is placed just above the sibling. πŸ‘‘
  • XmBELOW β€” the widget is placed just below the sibling. πŸ₯Ί

if the sibling parameter is not specified, then widget is restacked like this instead:

  • XmABOVE β€” the widget is placed at the top of the stack. main character energy fr fr 🌟
  • XmBELOW β€” the widget is placed at the bottom of the stack. humble era, we love to see it 🌸

for a complete definition of DropSite and its associated resources, see XmDropSite(3). iykyk πŸ’œ


XmDropSite(3), XmDropSiteRetrieve(3), and XmDropSiteQueryStackingOrder(3).

go read those too, they're iconic, no cap πŸ“šβœ¨


and that's the whole page, bestie!! πŸ’– this was XmDropSiteC...ackingOrder from the library call manual β€” the footer's little signature says so, no date drama attached, just pure library-call realness. πŸŽ€πŸ¦‹ slay responsibly 🫢