MirOS Manual: XtNumber(3), XtOffset(3), XtOffsetOf(3)


XtOffset(3Xt)             XT FUNCTIONS              XtOffset(3Xt)

NAME

     XtOffset, XtOffsetOf, XtNumber - determine the byte offset
     or number of array elements

SYNTAX

     Cardinal XtOffset(Type pointer_type, Field field_name);

     Cardinal XtOffsetOf(Type structure_type, Field field_name);

     Cardinal XtNumber(ArrayVariable array);

ARGUMENTS

     array     Specifies a fixed-size array.

     field_name
               Specifies the name of the field for which to cal-
               culate the byte offset.

     pointer_type
               Specifies a type that is declared as a pointer to
               the structure.

     structure_type
               Specifies a type that is declared as a structure.

DESCRIPTION

     The XtOffset macro is usually used to determine the offset
     of various resource fields from the beginning of a widget
     and can be used at compile time in static initializations.

     The XtOffsetOf macro expands to a constant expression that
     gives the offset in bytes to the specified structure member
     rom the beginning of the structure. It is normally used to
     statically initialize resource lists and is more portable
     than XtOffset, which serves the same function.

     The XtNumber macro returns the number of elements in the
     specified argument lists, resources lists, and other counted
     arrays.

SEE ALSO

     XtGetResourceList(3Xt), XtSetArg(3Xt)
     X Toolkit Intrinsics - C Language Interface
     Xlib - C Language X Interface

XFree86                   Version 4.5.0                         1

Generated on 2017-04-03 16:26:17 by $MirOS: src/scripts/roff2htm,v 1.88 2017/01/29 00:51:06 tg Exp $

These manual pages and other documentation are copyrighted by their respective writers; their source is available at our CVSweb, AnonCVS, and other mirrors. The rest is Copyright © 2002–2017 The MirOS Project, Germany.
This product includes material provided by mirabilos.

This manual page’s HTML representation is supposed to be valid XHTML/1.1; if not, please send a bug report — diffs preferred.