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

✨ XmGetMenuCursor ✨

okay so bestie, gather round, because we're talking about a little function from the XmGetMenuCursor(library call) manual and it's giving vintage πŸ’…


πŸ’– NAME πŸ’–

XmGetMenuCursor β€” a function that hands you the cursor ID for whatever menu cursor is currently in rotation πŸ–±οΈβœ¨


🌸 SYNOPSIS 🌸

#include <Xm/Xm.h>
Cursor XmGetMenuCursor(
Display * display);

πŸ¦‹ DESCRIPTION πŸ¦‹

So what does it actually do? XmGetMenuCursor goes and asks the menu cursor that this client is currently using on the display you point it at, and it returns that cursor ID. That's it, that's the whole vibe. πŸŽ€

And lowkey important: this function returns the menu cursor for the default screen of the display. Like, it doesn't care about your other screens, it's locked in on the default one, periodt.

⚠️ NOTE: XmGetMenuCursor is obsolete and only exists for compatibility with previous releases. So bestie, please don't build your whole personality around it. Instead of using this function, call XtGetValues for the XmScreen resource XmNmenuCursor. That's the main character move now. πŸ‘‘
  • display β€” specifies the display whose menu cursor is to be queried πŸ‘€

πŸ’œ RETURN πŸ’œ

It returns the cursor ID for the current menu cursor... or it returns the value None if a cursor isn't defined yet 😭

And when is a cursor not defined, you ask? A cursor will not be defined if the application makes this call before the client has created any menus on the specified display. So like, don't come knocking before the menus exist, okay? There's literally nothing there yet. πŸ™ˆ



and that's the whole page, bestie 🫢 this lil blast-from-the-past lives in the XmGetMenuCursor(library call) manual β€” go forth and call XtGetValues instead, fr fr πŸ’–βœ¨πŸŒΈ