XMSTRINGTABLEPARSESTRINGARRAY(3)
β¨ XmStringTableParseStringArray β¨
okay bestie, welcome to the library call corner of your manual, this one is XmStringTableParseStringArray(3) and it's literally the glow-up function that takes a whole array of strings and turns them into a compound string table. no cap. π
πΈ NAME πΈ
XmStringTableParseStringArray β a convenience function that converts an array of strings to a compound string table π¦
β¨ SYNOPSIS β¨
#include <Xm/Xm.h>
XmStringTable XmStringTableParseStringArray(
XtPointer *strings,
Cardinal count,
XmStringTag tag,
XmTextType type,
XmParseTable parse,
Cardinal parse_count,
XtPointer call_data);
π DESCRIPTION π
so here's the tea, bestie π β XmStringTableParseStringArray takes an array of strings, allocates an XmStringTable with an equal number of slots, calls XmStringParseText on each string in strings, and inserts the resulting XmString in the corresponding slot in the XmStringTable. it's giving factory line but make it fabulous β¨
stringsβ specifies an array of strings of characters as determined bytype. πcountβ specifies the number of strings instrings. count them, queen, don't guess π’tagβ specifies the tag to be used in creating the result. the type of tag created (charset or locale) depends on the type of the text and the value given. if the value specified isNULL, andtypeindicates that a charset tag should be created, then the tag will have the value ofXmFONTLIST_DEFAULT_TAG. iftypeindicates a locale tag, then the tag will have the value ofXmFONTLIST_DEFAULT_TAG. πtypeβ specifies the type of text to be passed in and the type of tag. if the type is eitherXmMULTIBYTE_TEXTorXmWIDECHAR_TEXT, a locale tag should be created. if the type isXmCHARSET_TEXT, a charset tag will be created. πparseβ specifies the parse table to be used. π§parse_countβ specifies the number of entries in the parse table. π«call_dataβ specifies data to be passed to the parse procedures. π
π RETURN π
returns a new XmStringTable. β¨ the function allocates space to hold the XmStringTable.
β οΈ okay this part is important, bestie, do not skip it: when the application no longer needs the returnedXmStringTable, the application should callXmStringFreecounttimes (that is, one time for each returned compound string) and then callXtFreeto deallocate theXmStringTableitself. that'scountcalls plus one. the way that memory leaks are NOT the vibe ππ
π₯ RELATED π₯
and that's the whole page, bestie π«Ά this was served to you from the library call manual β XmStringTa...StringArray(library call), exactly as it's titled up top and exactly as it's signed off at the bottom. no date stamp made it into the footer, so consider this your timeless little classic πβ stay hydrated, free your strings, and slay π
π
π¦ 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