[next] [previous] [contents]

  23.2 Using DECwindows Motif Bindings with BASIC
  The DECwindows Motif bindings consist of constant defi-
  nitions, global variable declarations, record structures, and
  function prototypes. The bindings include everything that is
  needed to do windows programming using the DECwindows
  Motif Application Programming Interface (API).

  The BASIC implementation of the DECwindows Motif bind-
  ings allow you to write to either the C version or the non-C
  version of the bindings. In either case you will want to re-
  fer to the DECwindows Motif OpenVMS User Interface before
  you start programming. For more detailed information about
  using Non-C Bindings, see DECwindows Motif for OpenVMS,
  Guide to Non-C Bindings
.

  BASIC$HELLOMOTIF.BAS, and BASIC$HELLOBURGER.BAS
  supplied on the kit as examples of using the BASIC language
  for windows programming.

  A BASIC user may code to the standard C DECwindows
  Motif bindings with the following exceptions:

  .
        Any identifiers longer than 31 characters must be trun-
        cated to 31 characters. Known instances include:

            S_ _XmTraverseObscuredCallbackStru (33)
            S_XmOperationChangedCallbackStruc (33)
            S_XmDragDropFinishCallbackStruct (32)
  .
        Any identifiers beginning with an underscore must have
        the underscore dropped. Known instances include:

            _DXmPrintFormatStruct
            _DXmPrintOptionMenuStruct
            _XA_MOTIF_BINDINGS
            _XA_MOTIF_WM_FRAME
            _XA_MOTIF_WM_HINTS
            _XA_MOTIF_WM_INFO
            _XA_MOTIF_WM_MENU
            _XA_MOTIF_WM_MESSAGES
            _XA_MOTIF_WM_OFFSET
            _XA_MWM_HINTS
            _XA_MWM_INFO
            _XA_MWM_MESSAGES
            _XmSDEFAULT_BACKGROUND
            _XmSDEFAULT_FONT
            _XmSecondaryResuourceDataRec
            _XmTraverseObscuredCallbackStru
            _XtCheckSubclassFlag
            _XtIsSubclassOf
  .
        The following list of identifiers are used either as both
        a data type and a field name or as a BASIC keyword.
        They cannot be used as is, but must have the suffix "_D"
        appended when used as a data type and the suffix "_F"
        appended when used as a field name.

            dimension
            display
            font
            name
            pixel
            screen
            size
            status
            substitution
            time
            value
            window