XMCLIPBOARDUNLOCK(3)
π XmClipboardUnlock π
okay bestie, gather round, because we're talking about XmClipboardUnlock β a clipboard function from the Xm library calls that unlocks the clipboard πβ¨ yes, the whole vibe is "let go of the thing so other apps can touch it."
β¨ SYNOPSIS β¨
like, here's the receipts, no cap:
#include <Xm/CutPaste.h>
int XmClipboardUnlock (display, window, remove_all_locks)
Display * display;
Window window;
Boolean remove_all_locks;
(void)
πΈ DESCRIPTION πΈ
XmClipboardUnlock unlocks the clipboard, which literally just means it enables the clipboard to be accessed by other applications. sharing is caring, periodt π«Ά
okay but here's the part that gets people: if you called XmClipboardLock multiple times, then you need the same number of calls to XmClipboardUnlock to actually unlock the clipboard β it's a nesting thing, not a one-and-done β unless you set remove_all_locks to True, in which case it clears the whole stack in one go. it's giving "unsubscribe from all" energy π
the args, one by one π
displayβ a pointer to theDisplaystructure that came back from a previous call toXOpenDisplayorXtDisplay. you know, the one you already have lying around.windowβ the window ID of a widget that relates the application window to the clipboard. you can grab it throughXtWindow. and listen: the same application instance should pass the same window ID to each of the clipboard functions that it calls. consistency is the whole look, iykyk πremove_all_locksβ whenTrue, it indicates that all nested locks should be removed. whenFalse, it indicates that only one level of lock should be removed. so like, one layer at a time, or scorched earth. your call bestie π
β RETURN β
here's what you get back:
XmClipboardSuccessβ the function was successful. slay, we ate πXmClipboardFailβ the function failed because the clipboard was not locked, or was locked by another application. π so awkward. not your clipboard, not your business.
π¦ RELATED π¦
the whole clipboard friend group, all in one place β go say hi:
XmClipboardCancelCopy(3)XmClipboardCopy(3)XmClipboardEndCopy(3)XmClipboardEndRetrieve(3)XmClipboardInquireCount(3)XmClipboardInquireFormat(3)XmClipboardInquireLength(3)XmClipboardInquirePendingItems(3)XmClipboardLock(3)XmClipboardRegisterFormat(3)XmClipboardRetrieve(3)XmClipboardStartCopy(3)XmClipboardStartRetrieve(3)XmClipboardUndoCopy(3)XmClipboardWithdrawFormat(3)
and that's the whole page, bestie π this one lives in the library call section of the manual under the name XmClipboardUnlock β same title up top, same title at the bottom, absolutely iconic of it. mwah, go unlock something ππ
π¦ 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