XMCOMBOBOX(3)

📦
version 2.3.8 · 3 versions
, in arch rolling, centos-stream 9, epel 10, fedora 43, fedora 44, nixos 26.05, nixpkgs unstable, opensuse-leap 16.0

yo bestie, welcome to XmComboBox from the library call manual 💖 this one is giving “text field plus list” energy, and we’re gonna unpack it fr fr.

✨ NAME ✨

XmComboBox — the ComboBox widget class. that’s the name, that’s the vibe, periodt 💅

🌈 SYNOPSIS 🌈

#include <Xm/ComboBox.h>

🦋 DESCRIPTION 🦋

Okay so XmComboBox combines the capabilities of a single-line TextField widget and a List widget. It lets users do operations like typing and pasting information, and it also gives them a list of possible choices they can select from to complete the TextField entry field. The list can either be displayed at all times or can be dropped down by the user. When the list portion of the ComboBox is hidden, users get a visual cue — a downward-pointing arrow — next to the TextField field. The position of the arrow relative to the TextField field depends on the XmNlayoutDirection resource of the widget. This version of the ComboBox is called the "drop-down" ComboBox. Drop-down ComboBoxes are useful when screen space is limited, or when users will complete the text entry field more often by typing text than by selecting the entry field text from the list. The user can access the drop-down ComboBox in either one of two ways:

  • By clicking and releasing <Btn1> on the downward-pointing arrow, which pops the list up, and the list stays up. A later selection of an item in the list will cause the item to appear in the text entry field, and the list will unpost itself.
  • By pressing <Btn1> on the downward-pointing arrow, dragging it to a list item, and then releasing it there, which selects that item. The list disappears, and the selected item appears in the text entry field.

The application provides an array of strings that fill the list. At creation time, string items can be passed to the ComboBox via an arglist. Each string becomes an item in the list, with the first string becoming the item in position 1, the second string becoming the item in position 2, and so on. The size of the list is set by specifying the number of items that are visible in the list (XmNvisibleItemCount). If the number of items in the list exceeds the number of items that are visible, a vertical scroll bar will automatically appear that allows the user to scroll through a large number of items.

ComboBox creates two child widgets: a TextField widget for entering text and a ScrolledWindow containing a List for the list of items. The name of the items list itself is List, and the name of the TextField is Text. The application or user can specify resource values for these widgets in a resource file, and the application can use XtNameToWidget (specifying "*List" for the items list or "*Text" for the TextField widget) to obtain the widget IDs of the descendant widgets. At creation time, ComboBox passes appropriate resource values in the creation arglist, including XmNitems, to the items list. Note that the result of providing the XmNdestroyCallback resource in the creation arglist is unspecified. The application should use the XtAddCallback function to add callbacks to the appropriate widget (TextField or List) after creating it.

bestie, that XmNdestroyCallback in the creation arglist thing? unspecified. do not play with it. use XtAddCallback after creation instead, okay? 🫶

ComboBox forces the following resource values on its List child:

  • If XmNcomboBoxType is XmCOMBO_BOX, XmNtraversalOn is forced to False.
  • XmNhighlightThickness is forced to 2 in a drop-down ComboBox and to 0 in other types of ComboBoxes.
  • XmNborderWidth is forced to 0.
  • XmNnavigationType is forced to XmNONE.
  • XmNselectionPolicy is forced to XmBROWSE_SELECT.
  • XmNlistSizePolicy is forced to XmVARIABLE.
  • XmNspacing is forced to 0.
  • XmNvisualPolicy is forced to XmVARIABLE.
  • XmNselectedPositions is forced to NULL.
  • XmNselectedPositionsCount is forced to 0.

When XmNcomboBoxType is XmDROP_DOWN_LIST, ComboBox forces the following resource values on its TextField child:

  • XmNeditable is forced to False.
  • XmNcursorPositionVisible is forced to False.
  • XmNshadowThickness is forced to 0.

By contrast, when XmNcomboBoxType is XmCOMBO_BOX or XmDROP_DOWN_COMBO_BOX, ComboBox forces the following resource values on its TextField child:

  • XmNeditable is forced to True.
  • XmNcursorPositionVisible is forced to True.
  • XmNeditMode is forced to XmSINGLE_LINE_EDIT.

ComboBox always forces the values of the following resources on the TextField:

  • XmNnavigationType is forced to XmNONE.
  • XmNhighlightThickness is forced to 0.
  • XmNborderWidth is forced to 0.

ComboBox allows a single item to be selected in two ways: by selecting the desired item from the List or by entering text into the TextField. ComboBox does not automatically select a list item if the user types that string into the TextField. It selects the item when the user presses KActivate or moves the focus. ComboBox supports the Browse Select selection model of List (see the XmList reference page for a description of this model), so selections are mutually exclusive. Selecting an item from the list causes that item to be displayed in the TextField portion of the ComboBox. If an application sets the XmNvalue resource of TextField, that string is shown in the TextField. If the application has not provided any list items, or if there is no current selection, the TextField is empty.

The TextField in the ComboBox widget can be either editable or noneditable, depending on the value of the XmNcomboBoxType resource.

If the TextField is editable, the user can type into it. When the user presses the Return key, the ComboBox will compare the typed entry to the items in the List. If there is an exact match, then the matched List item is selected. If the application wishes to validate the entered text (for example, to ensure that the typed selection is a valid one), it can do so by setting XmNmodifyVerifyCallback on the TextField widget.

If the TextField is noneditable, typing text may invoke a matching algorithm that will attempt to match the entered text with items in the list. The specific matching algorithm applied, which may be none, is determined by the value of the XmNmatchBehavior resource in ComboBox, which can be either XmNONE or XmQUICK_NAVIGATE. A value of XmNONE indicates that no matching algorithm will occur. A value of XmQUICK_NAVIGATE indicates that when the List widget has focus, one-character navigation is supported. In this algorithm, if the typed character is the initial character of some item in the List, this algorithm causes that item to be navigated to and selected, and the item is displayed in the TextField. Subsequently typing the same character will cycle among the items with the same first character.

Regardless of the selection mechanism used (either selected directly from the List or typed into the TextField), when an item in the List is selected, that item is highlighted in the List. In addition, the selected item is displayed in the TextField of the ComboBox. If the user performs an action that would move focus away from ComboBox, or selects a List item, the XmNselectionCallback callbacks are invoked to notify the application of the current contents of the TextField (or choice). The application then takes whatever action is required based on those contents (or choice).

ComboBox uses the XmQTspecifyRenderTable trait and holds the XmQTaccessTextual trait.

👑 Classes 👑

XmComboBox inherits behavior, resources, and traits from Core, Composite, and XmManager classes.

The class pointer is xmComboBoxWidgetClass.

The class name is XmComboBox.

✨ New Resources ✨

okay bestie, the following table defines a set of widget resources used by the programmer to specify data. You can also set the resource values for the inherited classes to set attributes for this widget. To reference a resource by name or by class in a .Xdefaults file, remove the XmN or XmC prefix and use the remaining letters. To specify one of the defined values for a resource in a .Xdefaults file, remove the Xm prefix and use the remaining letters (in either lowercase or uppercase, but include any underscores between words). The codes in the access column indicate if the given resource can be at creation time (C), set by using XtSetValues (S), retrieved by using XtGetValues (G), or is not applicable (N/A). 💖

Here's the XmComboBox Resource Set — every single one, no skips:

  • XmNarrowSize — Class: XmCArrowSize · Type: Dimension · Default: dynamic · Access: CSG
  • XmNarrowSpacing — Class: XmCArrowSpacing · Type: Dimension · Default: dynamic · Access: CSG
  • XmNcolumns — Class: XmCColumn · Type: short · Default: dynamic · Access: CSG
  • XmNcomboBoxType — Class: XmCComboBoxType · Type: unsigned char · Default: XmCOMBO_BOX · Access: CG
  • XmNfontList — Class: XmCFontList · Type: XmFontList · Default: NULL · Access: CSG
  • XmNhighlightThickness — Class: XmCHighlightThickness · Type: Dimension · Default: 2 · Access: CSG
  • XmNitemCount — Class: XmCItemCount · Type: int · Default: dynamic · Access: CSG
  • XmNitems — Class: XmCItems · Type: XmStringTable · Default: dynamic · Access: CSG
  • XmNlist — Class: XmCList · Type: Widget · Default: dynamic · Access: G
  • XmNmarginHeight — Class: XmCMarginHeight · Type: Dimension · Default: 2 · Access: CSG
  • XmNmarginWidth — Class: XmCMarginWidth · Type: Dimension · Default: 2 · Access: CSG
  • XmNmatchBehavior — Class: XmCMatchBehavior · Type: unsigned char · Default: dynamic · Access: CSG
  • XmNpositionMode — Class: XmCPositionMode · Type: XtEnum · Default: XmZERO_BASED · Access: CG
  • XmNrenderTable — Class: XmCRenderTable · Type: XmRenderTable · Default: dynamic · Access: CSG
  • XmNselectedItem — Class: XmCSelectedItem · Type: XmString · Default: NULL · Access: CSG
  • XmNselectedPosition — Class: XmCSelectedPosition · Type: int · Default: dynamic · Access: CSG
  • XmNselectionCallback — Class: XmCCallback · Type: XmCallbackList · Default: NULL · Access: C
  • XmtextField — Class: XmCTextField · Type: Widget · Default: dynamic · Access: G
  • XmNvisibleItemCount — Class: XmCVisibleItemCount · Type: int · Default: 10 · Access: CSG

XmNarrowSize

Specifies the width of the arrow. The default size depends on the size of the text, as well as the size of the ComboBox. It's giving "I scale with the vibes" energy. 💅

XmNarrowSpacing

Specifies the space between the text and arrow visual in pixels. The default value is obtained from the XmNmarginWidth resource. So it lowkey inherits the margin vibe. ✨

XmNcolumns

Specifies the number of columns in the text field. If unset, the text field's value is used. Refer to the XmTextField man page for more detailed information. Go read that one if you want the full tea. 📖

XmNcomboBoxType

Specifies the type of ComboBox to be created. This can be one of the following:

  • XmCOMBO_BOX — Generates a ComboBox where the list is always displayed, and the text entry field is editable.
  • XmDROP_DOWN_COMBO_BOX — Generates a ComboBox where the list is hidden unless specifically requested, and the text entry field is editable.
  • XmDROP_DOWN_LIST — Generates a ComboBox where the list is hidden unless specifically requested, and the text entry field is noneditable.

Pick your fighter wisely, bestie. 🎀

XmNfontList

Specifies the fontlist associated with XmComboBox. The fontlist is an obsolete construct, and has been superseded by the render table. It is included for compatibility with earlier versions of Motif, and for applications that do not easily support render tables. The default fontlist is derived from the default render table, and if both a fontlist and a render table are specified, the render table takes precedence. So like… the render table ate and left no crumbs. Periodt. 💀

XmNhighlightThickness

Specifies the thickness of the highlighting rectangle. That's literally it. Simple. Clean. Iconic. ✨

XmNitemCount

Specifies the number of items in the list. If unset, the lists's value is used. Refer to the XmList man page for more detailed information. Yes, "lists's" — we don't make the rules, we just keep every detail. 😭

XmNitems

Specifies the items in the list. If unset, the lists's value is used. Refer to the XmList man page for more detailed information. Again with the list's value — it's a whole thing. 🦋

XmNlist

The list widget. Just… the list widget. Main character energy right there. 👑

XmNmarginWidth

Specifies the horizontal spacing between the child widgets and the boundary of the ComboBox. Give those widgets some room to breathe, bestie. 🌸

  • XmNmarginHeight — how much vertical breathing room sits between the child widgets and the edges of the ComboBox 💫 lowkey the personal space of your widget.
  • XmNmatchBehavior — bestie, this is the whole matching algorithm, the ~vibe check~ that decides how the text you typed into the TextField field gets matched against the items in the list. Current values are XmNONE and XmQUICK_NAVIGATE, like so:
    • XmNONE — there's literally no matching algorithm assigned. That's it. That's the whole personality.
    • XmQUICK_NAVIGATE — only valid for noneditable ComboBoxes (aka the XmNcomboBoxType resource value XmDROP_DOWN_LIST). This algorithm supports 1-character navigation when the List widget has focus 🎯 If the character you typed is the initial character of some item in the List, this algorithm causes that item to be navigated to and selected. And then? Typing that same character again will cycle among the items with the same first character. it's giving keyboard shortcuts, fr fr 👑
  • XmNpositionMode — controls how the value of the XmNselectedPosition resource and the item_position field of the callback structure are gonna be interpreted. Heads up tho: the convenience functions XmComboBoxDeletePos and XmComboBoxAddItem are not affected by this resource, and (just like XmList) they always use 1-based positions. periodt. Valid values for this resource are:
    • XmZERO_BASED — (DtComboBox compatibility mode: default) XmNselectedPosition is in [0,itemcount-1]. The item_position in the XmComboBoxCallbackStruct is 0 if the first element in the list was selected. And ngl, plot twist: 0 is also returned if no element in the list was selected (that is, a new item was entered in the text field). yeah. ambiguous. we know. 🙈
    • XmONE_BASED — (Motif mode) Both the resource value and the callback fields are 1-based. This is consistent with other Motif widgets, so if you're a Motif girlie this is your home turf 💅
  • XmNrenderTable — the render table associated with the ComboBox ✨ This render table is used in both the TextField field and the List in the ComboBox. It's used in conjunction with the XmNvisibleItemCount resource of the List to determine the height of the ComboBox widget. And if this value is NULL at initialization, and if the widget parent is XmBulletinBoard or its subclasses, VendorShell or its subclasses, or XmMenuShell, then the widget parent provides the default render table associated with the widget 🫶 Also: if both a render table and a fontlist are specified, the render table will take precedence. sorry fontlist, she ate and you didn't 😌
  • XmNselectedItem — a compound string that represents the current selection of the ComboBox. The selected item is the content of the ComboBox text entry field. literally the main character of the text box 🌟
  • XmNselectedPosition — if the selection in the ComboBox is an item in the list, this is the index of the selected item in the list. If no item in the list is selected, this is 0. no item, no index, just vibes and a zero 💀
  • XmNselectionCallback — the list of callbacks called when an item is selected 🎀 The reason field in the XmComboBoxCallbackStruct is XmCR_SELECT.
  • XmNtextField — the text field widget. yeah that's it, that's the whole description, she's short and she's iconic 🦋
  • XmNvisibleItemCount — the number of visible items in the list 👀 This will override any value specified for the list, so don't even try it. Refer to the XmList man page for more detailed information.

✨ Inherited Resources ✨

okay bestie so ComboBox is not doing all this alone — it's inheriting behavior and resources from its superclasses, like a nepo baby but make it useful 💅. The tables below are the full tea. And fr, if you want the complete description of any single resource, go read the reference page for the superclass it came from, periodt.

👑 XmManager Resource Set 👑

  • XmNbottomShadowColor — class XmCBottomShadowColor, type Pixel, default dynamic, access CSG
  • XmNbottomShadowPixmap — class XmCBottomShadowPixmap, type Pixmap, default XmUNSPECIFIED_PIXMAP, access CSG
  • XmNforeground — class XmCForeground, type Pixel, default dynamic, access CSG
  • XmNhelpCallback — class XmCCallback, type XtCallbackList, default NULL, access C
  • XmNhighlightColor — class XmCHighlightColor, type Pixel, default dynamic, access CSG
  • XmNhighlightPixmap — class XmCHighlightPixmap, type Pixmap, default dynamic, access CSG
  • XmNinitialFocus — class XmCInitialFocus, type Widget, default NULL, access CSG
  • XmNlayoutDirection — class XmCLayoutDirection, type XmDirection, default dynamic, access CG
  • XmNnavigationType — class XmCNavigationType, type XmNavigationType, default XmSTICKY_TAG_GROUP, access CSG
  • XmNpopupHandlerCallback — class XmCCallback, type XtCallbackList, default NULL, access C
  • XmNshadowThickness — class XmCShadowThickness, type Dimension, default 2, access CSG
  • XmNstringDirection — class XmCStringDirection, type XmStringDirection, default dynamic, access CG
  • XmNtopShadowColor — class XmCTopShadowColor, type Pixel, default dynamic, access CSG
  • XmNtopShadowPixmap — class XmCTopShadowPixmap, type Pixmap, default dynamic, access CSG
  • XmNtraversalOn — class XmCTraversalOn, type Boolean, default True, access CSG
  • XmNunitType — class XmCUnitType, type unsigned char, default dynamic, access CSG
  • XmNuserData — class XmCUserData, type XtPointer, default NULL, access CSG

🦋 Composite Resource Set 🦋

  • XmNchildren — class XmCReadOnly, type WidgetList, default NULL, access G
  • XmNinsertPosition — class XmCInsertPosition, type XtOrderProc, default NULL, access CSG
  • XmNnumChildren — class XmCReadOnly, type Cardinal, default 0, access G

🌈 Core Resource Set 🌈

  • XmNaccelerators — class XmCAccelerators, type XtAccelerators, default dynamic, access CSG

...and the inherited resource train keeps rolling, bestie, hop back on 🚂

  • XmNancestorSensitive — class XmCSensitive, type Boolean, default dynamic, access G
  • XmNbackground — class XmCBackground, type Pixel, default dynamic, access CSG
  • XmNbackgroundPixmap — class XmCPixmap, type Pixmap, default XmUNSPECIFIED_PIXMAP, access CSG
  • XmNborderColor — class XmCBorderColor, type Pixel, default XtDefaultForeground, access CSG
  • XmNborderPixmap — class XmCPixmap, type Pixmap, default XmUNSPECIFIED_PIXMAP, access CSG
  • XmNborderWidth — class XmCBorderWidth, type Dimension, default 0, access CSG
  • XmNcolormap — class XmCColormap, type Colormap, default dynamic, access CG
  • XmNdepth — class XmCDepth, type int, default dynamic, access CG
  • XmNdestroyCallback — class XmCCallback, type XtCallbackList, default NULL, access C
  • XmNheight — class XmCHeight, type Dimension, default dynamic, access CSG
  • XmNinitialResourcesPersistent — class XmCInitialResourcesPersistent, type Boolean, default True, access C
  • XmNmappedWhenManaged — class XmCMappedWhenManaged, type Boolean, default True, access CSG
  • XmNscreen — class XmCScreen, type Screen *, default dynamic, access CG
  • XmNsensitive — class XmCSensitive, type Boolean, default True, access CSG
  • XmNtranslations — class XmCTranslations, type XtTranslations, default dynamic, access CSG
  • XmNwidth — class XmCWidth, type Dimension, default dynamic, access CSG
  • XmNx — class XmCPosition, type Position, default 0, access CSG
  • XmNy — class XmCPosition, type Position, default 0, access CSG

that's the whole inherited lineup, and honestly? iconic. every single one. 💜

🎀 Callback Information 🎀

okay so when a callback fires, you don't just get vibes — you get a whole struct, and here's exactly what's inside it:

A pointer to the following structure is passed to each callback. The callback structure is defined as follows:

typedef struct
{
        int reason;
        XEvent *event;
        XmString item_or_text;
        int item_position;
} XmComboBoxCallbackStruct;
  • reason — tells you why the callback got invoked. The whole "who invited you here" of it all.
  • event — points to the XEvent that triggered the callback. It can be NULL, so pls don't assume it's always there, bestie. 🙈
  • item_or_text — the contents of the text field at the time the event caused the callback.
⚠️ heads up fr fr: item_or_text points to a temporary storage space that gets reused after the callback is finished. So if your application needs to save the item, you have to copy item_or_text into its own data space. Do not just hold onto the pointer and expect it to still be there later, because it will NOT be there later. 😭
  • item_position — the position of item in the list's XmNitems 1-based array. And if this is 0? That means the item_or_text was not selected from the List. Zero literally means "not from the List," no cap. 💅

✨ Translations ✨

The ComboBox translations are listed below.

The following key names are listed in the X standard key event translation table syntax. This format is the one used by Motif to specify the widget actions corresponding to a given key. A brief overview of the format is provided under VirtualBindings(3). For a complete description of the format, please refer to the X Toolkit Instrinsics Documentation.

Note: the KPageUp and KPageDown translations do not take effect unless the List child widget is posted. Like, they're just out here doing nothing until that List is posted. 🫠
<Btn1Down>:
          CBArmAndDropDownList()

<Btn1Up>: CBDisarm()

The following lists the List translations in the drop-down list. When ComboBox XmNcomboBoxType is XmDROP_DOWN_LIST, <osfActivate>, <osfCancel>, and Return are overriden by ComboBox actions.

  • :c <Key><osfDown>: → CBDropDownList()
  • :c <Key><osfUp>: → CBDropDownList()
  • :<Key><osfCancel>: → CBCancel()
  • :<Key><osfActivate>: → CBActivate()
  • ∼s ∼m ∼a<Key>Return: → CBActivate()

that Return one is doing the most and honestly? respect. 👑

💫 Accelerators 💫

The following accelerators are added to ComboBox and its children. The accelerators may not directly correspond to a translation table. If the translation is not listed below, it may depend on the context of the event.

and yes bestie, that "it depends on the context" line is doing a lot of heavy lifting, but it's the truth — some of these only show up depending on what's going on when the event lands. 🦋

Okay so here's the rest of the key bindings, bestie. These are the ones for the drop-down list and stuff:

:c <Key><osfUp>:
          CBDropDownList()

:<Key><osfUp>:
          CBListAction(Up)

:c <Key><osfDown>:
          CBDropDownList()

:<Key><osfDown>:
          CBListAction(Down)

:c <Key><osfBeginLine>:
          CBListAction(ListBeginData)

:c <Key><osfEndLine>:
          CBListAction(ListEndData)

:<Key><osfPageUp>:
          CBListAction(ListPrevPage)

:<Key><osfPageDown>:
          CBListAction(ListNextPage)

Oh and btw, a drop-down ComboBox also adds accelerators to its List child. Aside from the ones we just listed, those accelerators are literally the default TextField key translations. 💅

✨ Action Routines ✨

The XmComboBox action routines are as follows, and yes, we're going through every single one:

  • CBActivate() — Calls the XmNselectionCallback callbacks. If the XmNcomboBoxType is XmDROP_DOWN_COMBO_BOX or XmDROP_DOWN_LIST, it unposts the list. If the parent is a manager, passes the event to the parent. Slay. 💖
  • CBArmAndDropDownList() — If the pointer is within the down arrow, draws the shadow of the arrow in the selected state, and then posts the list. So dramatic. ✨
  • CBCancel() — If the XmNcomboBoxType is XmDROP_DOWN_COMBO_BOX or XmDROP_DOWN_LIST, pops down the list. If the parent is a manager, passes the event to the parent. 🎀
  • CBDisarm() — Redraws the arrow in an unselected state. Simple. Clean. Iconic. 🦋
  • CBDropDownList() — If XmNcomboBoxType is XmDROP_DOWN or XmDROP_DOWN_LIST, and list is not displayed, posts the list. If list is displayed, it unposts the list. Toggle queen. 💅
  • CBListAction(ListBeginData) — Moves the location cursor to the first item in the list. In Normal Mode, this also deselects any current selection, selects the first item in the list, and calls the XmNbrowseSelectionCallback selection callback. Main character energy fr fr. 👑
  • CBListAction(ListEndData) — Moves the location cursor to the last item in the list. In Normal Mode, this also deselects any current selection, selects the last item in the list, and calls the XmNbrowseSelectionCallback selection callback. End of the line, bestie. 🌈
  • CBListAction(ListPrevPage) — Scrolls the list to the previous page, moving the location cursor to a new item. This action also selects the new item, deselects any current selection, and calls the XmNbrowseSelectionCallback callbacks. If the ComboBox is not a drop-down type, then this action does nothing. No drop-down? No service. 💀
  • CBListAction(ListNextPage) — Scrolls the list to the next page, moving the location cursor to a new item. This action also selects the new item, deselects any current selection, and calls the XmNbrowseSelectionCallback callbacks. If the ComboBox is not a drop-down type, then this action does nothing. Same energy as above. 🙈
  • CBListAction(Up) — Moves the location cursor to the previous item in the list. This action also selects the previous item, deselects any current selection, and calls the XmNbrowseSelectionCallback callbacks. Note that, unlike the List ListPrevItem action, this action wraps around. So it's giving circular. 🌀
  • CBListAction(Down) — Moves the location cursor to the next item in the list. This action also selects the next item, deselects any current selection, and calls the XmNbrowseSelectionCallback callbacks. Note that, unlike the List ListNextItem action, this action wraps around. Also circular. 🔥

🦋 Virtual Bindings 🦋

The bindings for virtual keys are vendor specific, so like, check your vendor. For info about bindings for virtual buttons and keys, see VirtualBindings(3). Periodt. 💜

🚨 ERRORS/WARNINGS 🚨

The toolkit will literally display a warning if the application tries to set the value of XmNlist or the XmNtextField resource, which are read-only (marked G in the resource table). So don't do that. It's not the vibe. 🚫

And that's a wrap on the XmComboBox(library call) page! The date is whatever the man page says, but you know the vibe. Byeee bestie, stay slaying those ComboBoxes 💖✨🦋

📦 where this page comes from