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

🌸 XmForm(library call) 🌸

👑 NAME 👑

XmForm — The Form widget class

✨ SYNOPSIS ✨

#include <Xm/Form.h>

💖 DESCRIPTION 💖

Okay bestie, so Form is a container widget with no input semantics of its own. Constraints get placed on the children of the Form to define attachments for each of the child’s four sides. These attachments can be to the Form, to another child widget or gadget, to a relative position within the Form, or to the initial position of the child. And these attachments? They determine the layout behavior of the Form when resizing occurs. Periodt.

The default value for XmNinitialFocus is the value of XmNdefaultButton.

Following are some important considerations in using a Form:

  • Every child must have an attachment on either the left or the right. If initialization or XtSetValues leaves a widget without such an attachment, the result depends upon the value of XmNrubberPositioning.
    • If XmNrubberPositioning is False, the child is given an XmNleftAttachment of XmATTACH_FORM and an XmNleftOffset equal to its current x value.
    • If XmNrubberPositioning is True, the child is given an XmNleftAttachment of XmATTACH_POSITION and an XmNleftPosition proportional to the current x value divided by the width of the Form.
    • In either case, if the child has not been previously given an x value, its x value is taken to be 0 (zero), which places the child at the left side of the Form.
  • If you want to create a child without any attachments, and then later (for example, after creating and managing it, but before realizing it) give it a right attachment through XtSetValues, you must set its XmNleftAttachment to XmATTACH_NONE at the same time.
  • The XmNresizable resource controls only whether a geometry request by the child will be granted. It has no effect on whether the child’s size can be changed because of changes in geometry of the Form or of other children.
  • Every child has a preferred width, based on geometry requests it makes (whether they are granted or not).
  • If a child has attachments on both the left and the right sides, its size is completely controlled by the Form. It can be shrunk below its preferred width or enlarged above it, if necessary, due to other constraints. In addition, the child’s geometry requests to change its own width may be refused.
  • If a child has attachments on only its left or right side, it will always be at its preferred width (if resizable, otherwise at is current width). This may cause it to be clipped by the Form or by other children.
  • If a child’s left (or right) attachment is set to XmATTACH_SELF, its corresponding left (or right) offset is forced to 0 (zero). The attachment is then changed to XmATTACH_POSITION, with a position that corresponds to the x value of the child’s left (or right) edge. To fix the position of a side at a specific x value, use XmATTACH_FORM or XmATTACH_OPPOSITE_FORM with the x value as the left (or right) offset.
  • Unmapping a child has no effect on the Form except that the child is not mapped.
  • Unmanaging a child unmaps it. If no other child is attached to it, or if all children attached to it and all children recursively attached to them are also all unmanaged, all of those children are treated as if they did not exist in determining the size of the Form.
  • When using XtSetValues to change the XmNx resource of a child, you must simultaneously set its left attachment to either XmATTACH_SELF or XmATTACH_NONE. Otherwise, the request is not granted. If XmNresizable is False, the request is granted only if the child’s size can remain the same.
  • A left (or right) attachment of XmATTACH_WIDGET, where XmNleftWidget (or XmNrightWidget) is NULL, acts like an attachment of XmATTACH_FORM.
  • If an attachment is made to a widget that is not a child of the Form, but an ancestor of the widget is a child of the Form, the attachment is made to the ancestor.

All these considerations are true of top and bottom attachments as well, with top acting like left, bottom acting like right, y acting like x, and height acting like width.

🦋 Classes 🦋

Form inherits behavior, resources, and traits from Core, Composite, Constraint, XmManager, and XmBulletinBoard.

The class pointer is xmFormWidgetClass.

The class name is XmForm.

🌈 New Resources 🌈

The following table defines a set of widget resources used by the programmer to specify data. The programmer 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 set at creation time (C), set by using XtSetValues (S), retrieved by using XtGetValues (G), or is not applicable (N/A).

💫 XmForm Resource Set 💫

  • XmNfractionBase — Class: XmCMaxValue, Type: int, Default: 100, Access: CSG

Specifies the denominator used in calculating the relative position of a child widget using XmATTACH_POSITION constraints. The value must not be 0 (zero).

If the value of a child’s XmNleftAttachment (or XmNrightAttachment) is XmATTACH_POSITION, the position of the left (or right) side of the child is relative to the left side of the Form and is a fraction of the width of the Form. This fraction is the value of the child’s XmNleftPosition (or XmNrightPosition) resource divided by the value of the Form’s XmNfractionBase.

If the value of a child’s XmNtopAttachment (or XmNbottomAttachment) is XmATTACH_POSITION, the position of the top (or bottom) side of the child is relative to the top side of the Form and is a fraction of the height of the Form. This fraction is the value of the child’s XmNtopPosition (or XmNbottomPosition) resource divided by the value of the Form’s XmNfractionBase.

  • XmNhorizontalSpacing — Class: XmCSpacing, Type: Dimension, Default: 0, Access: CSG

Specifies the offset for right and left attachments. This resource is only used if no offset resource is specified (when attaching to a widget), or if no margin resource is specified (when attaching to the Form).

  • XmNrubberPositioning — Class: XmCRubberPositioning, Type: Boolean, Default: False, Access: CSG

Indicates the default near (left) and top attachments for a child of the Form. (Note that whether this resource actually applies to the left or right side of the child and its attachment depends on the value of the XmNlayoutDirection.)

The default left attachment is applied whenever initialization or XtSetValues leaves the child without either a left or right attachment. The default top attachment is applied whenever initialization or XtSetValues leaves the child without either a top or bottom attachment.

If this Boolean resource is set to False, XmNleftAttachment and XmNtopAttachment default to XmATTACH_FORM, XmNleftOffset defaults to the current x value of the left side of the child, and XmNtopOffset defaults to the current y value of the child. The effect is to position the child according to its absolute distance from the left or top side of the Form.

If this resource is set to True, XmNleftAttachment and XmNtopAttachment default to XmATTACH_POSITION, XmNleftPosition defaults to a value proportional to the current x value of the left side of the child divided by the width of the Form, and XmNtopPosition defaults to a value proportional to the current y value of the child divided by the height of the Form. The effect is to position the child relative to the left or top side of the Form and in proportion to the width or height of the Form.

  • XmNverticalSpacing — Class: XmCSpacing, Type: Dimension, Default: 0, Access: CSG

Specifies the offset for top and bottom attachments. This resource is only used if no offset resource is specified (when attaching to a widget), or if no margin resource is specified (when attaching to the Form).

🌸 XmForm Constraint Resource Set 🌸

okay bestie, so XmForm doesn't just vibe on its own — it hands every single one of its children a whole lil' toolkit of constraint resources 💖 and this is the complete roster. Every one of these gets set on the kid, not on the Form, and they all share the same access code, so you already know: CSG, every time, no cap 💅

Here's the whole fam, name → class → type → default → access:

  • XmNbottomAttachment — class XmCAttachment, type unsigned char, default XmATTACH_NONE, access CSG
  • XmNbottomOffset — class XmCOffset, type int, default 0, access CSG
  • XmNbottomPosition — class XmCPosition, type int, default 0, access CSG
  • XmNbottomWidget — class XmCWidget, type Widget, default NULL, access CSG
  • XmNleftAttachment — class XmCAttachment, type unsigned char, default XmATTACH_NONE, access CSG
  • XmNleftOffset — class XmCOffset, type int, default 0, access CSG
  • XmNleftPosition — class XmCPosition, type int, default 0, access CSG
  • XmNleftWidget — class XmCWidget, type Widget, default NULL, access CSG
  • XmNresizable — class XmCBoolean, type Boolean, default True, access CSG
  • XmNrightAttachment — class XmCAttachment, type unsigned char, default XmATTACH_NONE, access CSG
  • XmNrightOffset — class XmCOffset, type int, default 0, access CSG
  • XmNrightPosition — class XmCPosition, type int, default 0, access CSG
  • XmNrightWidget — class XmCWidget, type Widget, default NULL, access CSG
  • XmNtopAttachment — class XmCAttachment, type unsigned char, default XmATTACH_NONE, access CSG
  • XmNtopOffset — class XmCOffset, type int, default 0, access CSG
  • XmNtopPosition — class XmCPosition, type int, default 0, access CSG
  • XmNtopWidget — class XmCWidget, type Widget, default NULL, access CSG

now the tea on each one, one by one, no skips 🫖✨

XmNbottomAttachment 💖

this one says where the bottom side of the child is attached. it can be set to any of these:

  • XmATTACH_NONE — do not attach the bottom side of the child. she's free, she's floating, she's unbothered 🦋
  • XmATTACH_FORM — attach the bottom side of the child to the bottom side of the Form.
  • XmATTACH_OPPOSITE_FORM — attach the bottom side of the child to the top side of the Form. and lowkey, XmNbottomOffset can be used to determine the visibility of the child 👀
  • XmATTACH_WIDGET — attach the bottom side of the child to the top side of the widget or gadget specified in the XmNbottomWidget resource. but bestie, if XmNbottomWidget is NULL, then XmATTACH_WIDGET gets replaced by XmATTACH_FORM, and the child is attached to the bottom side of the Form instead. the swap is automatic, she adapts 💅
  • XmATTACH_OPPOSITE_WIDGET — attach the bottom side of the child to the bottom side of the widget or gadget specified in the XmNbottomWidget resource.
  • XmATTACH_POSITION — attach the bottom side of the child to a position that is relative to the top side of the Form and in proportion to the height of the Form. this position is determined by the XmNbottomPosition and XmNfractionBase resources.
  • XmATTACH_SELF — attach the bottom side of the child to a position that is proportional to the current y value of the bottom of the child divided by the height of the Form. this position is determined by the XmNbottomPosition and XmNfractionBase resources. and also, XmNbottomPosition gets set to a value proportional to the current y value of the bottom of the child divided by the height of the Form. she's literally defining herself, main character energy 👑

XmNbottomOffset ✨

specifies the constant offset between the bottom side of the child and the object to which it's attached. that relationship she establishes? it stays. no matter what resizing operations happen, the bond does not break 🫶

not me dropping a caveat: when this resource is explicitly set, the value of XmNverticalSpacing is ignored. like, completely. gone. periodt 💀

XmNbottomPosition 🌸

this resource is what determines the position of the bottom side of the child when the child's XmNbottomAttachment is set to XmATTACH_POSITION. in that case, the position of the bottom side of the child is relative to the top side of the Form and is a fraction of the height of the Form. and that fraction is the value of the child's XmNbottomPosition resource divided by the value of the Form's XmNfractionBase.

okay math check, bestie, follow along 🧮 if the child's XmNbottomPosition is 50, the Form's XmNfractionBase is 100, and the Form's height is 200, then the position of the bottom side of the child is 100. ate that up fr fr 🔥

XmNbottomWidget 🎀

specifies the widget or gadget to which the bottom side of the child is attached. this resource is used if the XmNbottomAttachment resource is set to either XmATTACH_WIDGET or XmATTACH_OPPOSITE_WIDGET.

also, a string-to-widget resource converter is automatically installed for use with this resource ✨ with that converter, the widget that is to be the value of the resource must exist at the time the widget that has the resource is created. no showing up late to this one, she needs to be there already 💅

XmNleftAttachment 🌈

specifies attachment of the near (left) side of the child. and quick note because this one trips people up: whether this resource actually applies to the left or right side of the child and its attachment depends on the value of the XmNlayoutDirection resource 👀

it can have the following values:

  • XmATTACH_NONE — do not attach the left side of the child. And if XmNrightAttachment is also XmATTACH_NONE? Then this value is ignored and the child just gets a default left attachment. the Form said "fine, I'll do it myself" 💅
  • XmATTACH_FORM — attach the left side of the child to the left side of the Form. clean. simple. iconic.
  • XmATTACH_OPPOSITE_FORM — attach the left side of the child to the right side of the Form (yes bestie, opposite, that's literally the whole vibe ✨). XmNleftOffset can be used to determine the visibility of the child.
  • XmATTACH_WIDGET — attach the left side of the child to the right side of the widget or gadget specified in the XmNleftWidget resource. And if XmNleftWidget is NULL? Then XmATTACH_WIDGET is replaced by XmATTACH_FORM, and the child is attached to the left side of the Form. it really said "no widget? bet, Form it is" 😭
  • XmATTACH_OPPOSITE_WIDGET — attach the left side of the child to the left side of the widget or gadget specified in the XmNleftWidget resource.
  • XmATTACH_POSITION — attach the left side of the child to a position that is relative to the left side of the Form and in proportion to the width of the Form. This position is determined by the XmNleftPosition and XmNfractionBase resources. 🎀
  • XmATTACH_SELF — attach the left side of the child to a position that is proportional to the current x value of the left side of the child divided by the width of the Form. This position is determined by the XmNleftPosition and XmNfractionBase resources. XmNleftPosition is set to a value proportional to the current x value of the left side of the child divided by the width of the Form. the way it just computes itself into place, main character energy fr fr 👑

🌸 XmNleftOffset 🌸

Specifies the constant offset between the near (left) side of the child and the object to which it is attached. (Note that whether this resource actually applies to the left or right side of the child and its attachment depends on the value of the XmNlayoutDirection resource.) The relationship established remains, regardless of any resizing operations that occur. And when this resource is explicitly set, the value of XmNhorizontalSpacing is ignored. no cap, it gets ghosted 💀

🦋 XmNleftPosition 🦋

This resource is used to determine the position of the near (left) side of the child when the child's XmNleftAttachment is set to XmATTACH_POSITION. (Note that whether this resource actually applies to the left or right side of the child and its attachment depends on the value of the XmNlayoutDirection resource.)

In this case, the position of the left side of the child is relative to the left side of the Form and is a fraction of the width of the Form. This fraction is the value of the child's XmNleftPosition resource divided by the value of the Form's XmNfractionBase. So like, for example — if the child's XmNleftPosition is 50, the Form's XmNfractionBase is 100, and the Form's width is 200, the position of the left side of the child is 100. math ate that 💅

💖 XmNleftWidget 💖

Specifies the widget or gadget to which the near (left) side of the child is attached. (Note that whether this resource actually applies to the left or right side of the child and its attachment depends on the value of the XmNlayoutDirection resource.) The XmNleftWidget resource is used if the XmNleftAttachment resource is set to either XmATTACH_WIDGET or XmATTACH_OPPOSITE_WIDGET.

A string-to-widget resource converter is automatically installed for use with this resource. With this converter, the widget that is to be the value of the resource must exist at the time the widget that has the resource is created. ⏰ order matters bestie, no time travel allowed

⭐ XmNresizable ⭐

This Boolean resource specifies whether or not a child's request for a new size is (conditionally) granted by the Form. If this resource is set to True the request is granted if possible. If this resource is set to False the request is always refused. always. the Form does not do negotiations 😤

If a child has both left and right attachments, its width is completely controlled by the Form, regardless of the value of the child's XmNresizable resource. If a child has a left or right attachment but not both, the child's XmNwidth is used in setting its width if the value of the child's XmNresizable resource is True. These conditions are also true for top and bottom attachments, with height acting like width. 🫶

🌈 XmNrightAttachment 🌈

Specifies attachment of the far (right) side of the child. (Note that whether this resource actually applies to the left or right side of the child and its attachment depends on the value of the XmNlayoutDirection resource.) It can have the following values:

  • XmATTACH_NONE — do not attach the right side of the child.
  • XmATTACH_FORM — attach the right side of the child to the right side of the Form.
  • XmATTACH_OPPOSITE_FORM — attach the right side of the child to the left side of the Form. XmNrightOffset can be used to determine the visibility of the child.
  • XmATTACH_WIDGET — attach the right side of the child to the left side of the widget or gadget specified in the XmNrightWidget resource. If XmNrightWidget is NULL, XmATTACH_WIDGET is replaced by XmATTACH_FORM, and the child is attached to the right side of the Form.
  • XmATTACH_OPPOSITE_WIDGET — attach the right side of the child to the right side of the widget or gadget specified in the XmNrightWidget resource.
  • XmATTACH_POSITION — attach the right side of the child to a position that is relative to the left side of the Form and in proportion to the width of the Form. This position is determined by the XmNrightPosition and XmNfractionBase resources.
  • XmATTACH_SELF — attach the right side of the child to a position that is proportional to the current x value of the right side of the child divided by the width of the Form. This position is determined by the XmNrightPosition and XmNfractionBase resources. XmNrightPosition is set to a value proportional to the current x value of the right side of the child divided by the width of the Form.

🎀 XmNrightOffset 🎀

Specifies the constant offset between the far (right) side of the child and the object to which it is attached. (Note that whether this resource actually applies to the left or right side of the child and its attachment depends on the value of the XmNlayoutDirection resource.) The relationship established remains, regardless of any resizing operations that occur. When this resource is explicitly set, the value of XmNhorizontalSpacing is ignored. same energy as its left-side twin, lowkey obsessed with the symmetry 💜

🧚 XmNrightPosition 🧚

This resource is used to determine the position of the far (right) side of the child when the child's XmNrightAttachment is set to XmATTACH_POSITION. (Note that whether this resource actually applies to the left or right side of the child and its attachment depends on the value of the XmNlayoutDirection resource.)

In this case the position of the right side of the child is relative to the left side of the Form and is a fraction of the width of the Form. This fraction is the value of the child's XmNrightPosition resource divided by the value of the Form's XmNfractionBase. For example, if the child's XmNrightPosition is 50, the Form's XmNfractionBase is 100, and the Form's width is 200, the position of the right side of the child is 100. 🍓

💜 XmNrightWidget 💜

Specifies the widget or gadget to which the far (right) side of the child is attached. (Note that whether this resource actually applies to the left or right side of the child and its attachment depends on the value of the XmNlayoutDirection resource.) The XmNrightWidget resource is used if the XmNrightAttachment resource is set to either XmATTACH_WIDGET or XmATTACH_OPPOSITE_WIDGET.

A string-to-widget resource converter is automatically installed for use with this resource. With this converter, the widget that is to be the value of the resource must exist at the time the widget that has the resource is created. 🙈 yes, same rule as XmNleftWidget, the converter does not wait around

🔥 XmNtopAttachment 🔥

Specifies attachment of the top side of the child. It can have following values:

  • XmATTACH_NONE — do not attach the top side of the child. If the XmNbottomAttachment resource is also XmATTACH_NONE, this value is ignored and the child is given a default top attachment.
  • XmATTACH_FORM — attach the top side of the child to the top side of the Form.
  • XmATTACH_OPPOSITE_FORM — attach the top side of the child to the bottom side of the Form. XmNtopOffset can be used to determine the visibility of the child.
  • XmATTACH_WIDGET — attach the top side of the child to the bottom side of the widget or gadget specified in the XmNtopWidget resource. If XmNtopWidget is NULL, XmATTACH_WIDGET is replaced by XmATTACH_FORM and the child is attached to the top side of the Form. ✨
  • XmATTACH_OPPOSITE_WIDGET — sticks the top side of the child to the top side of the widget or gadget you named over in the XmNtopWidget resource. top-to-top, matching energy, iconic 💅
    • XmATTACH_POSITION — sticks the top side of the child to a position that's relative to the top side of the Form and in proportion to the height of the Form. which position tho? that's decided by the XmNtopPosition and XmNfractionBase resources. math girlies rise 🎀
    • XmATTACH_SELF — sticks the top side of the child to a position that's proportional to the child's current y value divided by the height of the Form. again, XmNtopPosition and XmNfractionBase are the ones calling the shots. and plot twist: XmNtopPosition gets set to a value proportional to the current y value of the child divided by the height of the Form. so it writes back. main character behaviour, honestly 👑
  • XmNtopOffset — the constant offset between the top side of the child and the object it's attached to. the relationship you establish here stays no matter what resizing happens later — it does not budge, periodt. and heads up bestie: when you set this resource explicitly, the value of XmNverticalSpacing is just ignored. sorry to that resource 😭
  • XmNtopPosition — this one's here to figure out where the top side of the child goes when the child's XmNtopAttachment is set to XmATTACH_POSITION. in that case the top side of the child is positioned relative to the top side of the Form, as a fraction of the height of the Form. that fraction is the child's XmNtopPosition value divided by the Form's XmNfractionBase value. okay example time, stay with me:

so if the child's XmNtopPosition is 50, the Form's XmNfractionBase is 100, and the Form's height is 200 — then the position of the top side of the child is 100. slay, the math math'd ✨

  • XmNtopWidget — names the widget or gadget that the top side of the child gets attached to. this resource only does anything when XmNtopAttachment is set to either XmATTACH_WIDGET or XmATTACH_OPPOSITE_WIDGET. iykyk 🦋

a string-to-widget resource converter is automatically installed for use with this resource. and because of that converter: the widget that's gonna be the value of the resource must exist at the time the widget that has the resource is created. no time travel, no "i'll make it later" — it has to already be there, fr fr 🙈

🌈 Inherited Resources 🌈

Form doesn't do all of this alone, okay? it inherits behavior and resources from the superclasses described in the following tables. and for a complete description of each resource, you go check the reference page for that superclass. go give them their credit, they earned it 💖

okay bestie, the XmBulletinBoard resource set is giving full main character energy — here's every single one, fr fr, no skipping. 💖

  • XmNallowOverlap — class XmCAllowOverlap, type Boolean, default True, access CSG ✨
  • XmNautoUnmanage — class XmCAutoUnmanage, type Boolean, default True, access CG 🦋
  • XmNbuttonFontList — class XmCButtonFontList, type XmFontList, default dynamic, access CSG 🎀
  • XmNbuttonRenderTable — class XmCButtonRenderTable, type XmRenderTable, default dynamic, access CSG 🌸
  • XmNcancelButton — class XmCWidget, type Widget, default NULL, access SG 💅
  • XmNdefaultButton — class XmCWidget, type Widget, default NULL, access SG 🫶
  • XmNdefaultPosition — class XmCDefaultPosition, type Boolean, default True, access CSG 🌈
  • XmNdialogStyle — class XmCDialogStyle, type unsigned char, default dynamic, access CSG 💀
  • XmNdialogTitle — class XmCDialogTitle, type XmString, default NULL, access CSG 📝
  • XmNfocusCallback — class XmCCallback, type XtCallbackList, default NULL, access C 🔥
  • XmNlabelFontList — class XmCLabelFontList, type XmFontList, default dynamic, access CSG 🎀
  • XmNlabelRenderTable — class XmCLabelRenderTable, type XmRenderTable, default dynamic, access CSG 🦋
  • XmNmapCallback — class XmCCallback, type XtCallbackList, default NULL, access C 🗺️
  • XmNmarginHeight — class XmCMarginHeight, type Dimension, default 0, access CSG 📏
  • XmNmarginWidth — class XmCMarginWidth, type Dimension, default 0, access CSG 📐
  • XmNnoResize — class XmCNoResize, type Boolean, default False, access CSG 🚫
  • XmNresizePolicy — class XmCResizePolicy, type unsigned char, default XmRESIZE_ANY, access CSG 🔄
  • XmNshadowType — class XmCShadowType, type unsigned char, default XmSHADOW_OUT, access CSG 🌑
  • XmNtextFontList — class XmCTextFontList, type XmFontList, default dynamic, access CSG 🔤
  • XmNtextRenderTable — class XmCTextRenderTable, type XmRenderTable, default dynamic, access CSG 📋
  • XmNtextTranslations — class XmCTranslations, type XtTranslations, default NULL, access C 🔀
  • XmNunmapCallback — class XmCCallback, type XtCallbackList, default NULL, access C 🗑️

and that's the whole resource set, bestie — but hold up, there's literally more manual page coming, so don't go anywhere. 💅

XmManager Resource Set 💅

okay bestie, we’re in the resource zone now and it’s giving very much ✨iconic✨. Here’s the whole XmManager resource set — every Name, Class, Type, Default, and Access value, no skipping, periodt. 🫶

  • 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: dynamic; Access: CSG
  • XmNlayoutDirection — Class: XmCLayoutDirection; Type: XmDirection; Default: dynamic; Access: CG
  • XmNnavigationType — Class: XmCNavigationType; Type: XmNavigationType; Default: XmTAB_GROUP; Access: CSG
  • XmNpopupHandlerCallback — Class: XmCCallback; Type: XtCallbackList; Default: NULL; Access: C
  • XmNshadowThickness — Class: XmCShadowThickness; Type: Dimension; Default: dynamic; 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

and now the Composite set, because the plot thickens 🦋

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 🎀

okay bestie, here comes the whole lineup 💖 every single resource, in order, no skips, no cuts — class, type, default and access all accounted for. read it slow, it's giving encyclopedia but make it cute.

  • XmNaccelerators — class XmCAccelerators, type XtAccelerators, default dynamic, access N/A
  • 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

like… that's the whole set. nineteen icons, all accounted for, not one of them ghosted you 💅

✨ Translations ✨

short and sweet, no notes:

XmForm inherits translations from XmBulletinBoard.

that's it. that's the whole translation situation. it's giving "family recipe, handed down" 🫶

if you liked this page, the extended universe is right here — go read these next, bestie:

and that's a wrap on the whole page 🎀 you made it to the end, which is genuinely iconic of you ✨ this one's filed under XmForm(library call) — the library-call corner of the man pages, your fave neighborhood fr fr. go build something gorgeous with it, and remember: every option we listed is a promise, so use them kindly. byeee 💖🦋🌸

📦 where this page comes from