XMDIRECTIONMATCHPARTIAL(3)
π XmDirectionMatchPartial β like, the NAME section, bestie
Okay so this page is XmDirectionMatchPartial, a library call from the Motif/Xm world, and she's here to do exactly one thing: check one specific direction component of two direction values. That's it. That's the whole job. Iconic, honestly. β¨
πΈ SYNOPSIS πΈ
#include <Xm/Xm.h>
Boolean XmDirectionMatchPartial (d1, d2, dmask)
XmDirection d1;
XmDirection d2;
XmDirection dmask;
(void)
No cap, that's the whole signature. Three XmDirection args in, one Boolean out. Simple girl, simple life. π
π¦ DESCRIPTION π¦
So here's the tea: XmDirectionMatchPartial compares d1 and d2 along the direction component that you specify with dmask. Not the whole vibe β just the one slice you asked about. For example, if dmask equals XmVERTICAL_MASK, then the function will compare only the vertical components of d1 and d2. That's it, that's the whole point of the "Partial" in the name, periodt. π
d1β Specifies anXmDirectionvalue to check. (Your first little guy. π«Ά)d2β Specifies anXmDirectionvalue to check. (Your second little guy. They're getting compared. It's giving rivals-to-lovers, lowkey. π)dmaskβ Specifies the direction component along whichd1andd2are to be checked. Appropriate values fordmaskareXmHORIZONTAL_MASK,XmVERTICAL_MASK, andXmPRECEDENCE_MASK. Pick your fighter. π
fr fr, dmask is the whole main character here. You're literally telling the function which axis of the situation you care about. π
β¨ RETURN VALUES β¨
- Returns
Trueif thed1andd2match in the component specified bydmask - otherwise, returns
False
That's it. Binary queen. π
No shades of grey, no "maybe", just True or False and she moves on with her day. π₯
π RELATED INFORMATION π
Go read these too, they're all in the same friend group:
XmDirection(3)XmDirectionMatch(3)XmDirectionToStringDirection(3)XmStringDirection(3)XmStringDirectionToDirection(3)
And that's the whole page, bestie!! πβ¨ This was XmDirectionMatchPartial(library call) β yes, the same name as up top, the manual really said "bookends π" β go forth and check those direction components, you're doing amazing, slay, bye!! π¦π
π¦ where this page comes from
- alpine 3.24: motif-doc 2.5.2-r0 Β· LGPL-2.1-or-later
- arch rolling: openmotif 2.3.8-4 Β· LGPL-2.1-or-later
- centos-stream 9: motif-devel 2.3.4-32.el9 Β· LGPLv2+
- centos-stream 9: motif-devel 2.3.4-32.el9 Β· LGPLv2+
- epel 10: motif-devel 2.3.8-2.el10_2 Β· LicenseRef-Callaway-LGPLv2+
- fedora 43: motif-devel 2.3.8-1.fc43 Β· LicenseRef-Callaway-LGPLv2+
- fedora 43: motif-devel 2.3.8-1.fc43 Β· LicenseRef-Callaway-LGPLv2+
- fedora 43: motif-devel 2.3.8-2.fc43 Β· LicenseRef-Callaway-LGPLv2+
- fedora 43: motif-devel 2.3.8-2.fc43 Β· LicenseRef-Callaway-LGPLv2+
- fedora 44: motif-devel 2.3.8-3.fc44 Β· LicenseRef-Callaway-LGPLv2+
- fedora 44: motif-devel 2.3.8-3.fc44 Β· LicenseRef-Callaway-LGPLv2+
- nixos 26.05: motif 2.3.8
- nixpkgs unstable: motif 2.3.8
- opensuse-leap 16.0: motif-devel 2.3.8-bp160.1.1 Β· LGPL-2.1-or-later
- opensuse-leap 16.0: motif-devel 2.3.8-bp160.1.1 Β· LGPL-2.1-or-later
- opensuse-leap 16.0: motif-devel 2.3.8-bp160.1.1 Β· LGPL-2.1-or-later
- opensuse-leap 16.0: motif-devel 2.3.8-bp160.1.1 Β· LGPL-2.1-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms