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

✨ XmGetTearOffControl β€” NAME energy ✨

okay so bestie, this is XmGetTearOffControl from the library call manual (yes that's the whole header, we're keeping it cute and brief) πŸ’–

XmGetTearOffControl β€” a RowColumn function that obtains the widget ID for the tear-off control in a menu. that's the whole job. she does one thing and she does it flawlessly πŸ’…


🌸 SYNOPSIS 🌸

#include <Xm/RowColumn.h>
Widget XmGetTearOffControl(
Widget menu);

no cap, that's it. two lines and a dream 🫢


πŸ¦‹ DESCRIPTION πŸ¦‹

XmGetTearOffControl is literally the plug πŸ”Œ β€” she gives your application the means for obtaining the widget ID of the internally created tear-off control in a tear-off menu.

so here's the lore: RowColumn creates a tear-off control for a PulldownMenu or PopupMenu when the XmNtearOffModel resource is initialized or set to XmTEAR_OFF_ENABLED. periodt. the tear-off control is a widget that appears as the first element in the menu πŸ‘‘ β€” she's the main character, front of the line, always. the user tears off the menu by means of mouse or keyboard events in the tear-off control. iconic behavior, truly.

the tear-off control has Separator-like behavior. and once your application has obtained the widget ID of the tear-off control, it can set resources to specify the appearance of the control ✨. the application or the user can also set these resources in a resource file by using the name of the control, which is TearOffControl. and for a list of the resources the application or user can set, go see XmRowColumn(3) β€” she's got the receipts πŸ“œ

  • menu β€” Specifies the widget ID of the RowColumn PulldownMenu or PopupMenu

for more info on tear-off menus and a complete definition of RowColumn and its associated resources, see XmRowColumn(3). iykyk πŸ’œ


πŸ’€ RETURN πŸ’€

returns the widget ID for the tear-off control, or NULL if no tear-off control exists.

🚨 real talk, no cap: an application should not assume that the returned widget will be of any particular class. do not do it. i'm serious. don't be that girl πŸ™ˆ


okay that's the whole page, you ate that bestie πŸŽ€ go get that widget ID, and remember: this was the XmGetTearOffControl(library call) manual β€” that's the footer, that's the whole vibe, mwah πŸ’–βœ¨πŸ¦‹