MirOS Manual: XtGetKeysymTable(3), XtKeysymToKeycodeList(3)


XtGetKeysymTable(3Xt)     XT FUNCTIONS      XtGetKeysymTable(3Xt)

NAME

     XtGetKeysymTable, XtKeysymToKeycodeList - query keysyms and
     keycodes

SYNTAX

     Keysym* XtGetKeysymTable(Display* display, KeyCode*
          min_keycode_return, int *keysyms_per_keycode_return);

     void XtKeysymToKeycodeList(Display* display, KeySym keysym,
          KeyCode** keycodes_return, Cardinal* keycount_return);

ARGUMENTS

     display   Specifies the display whose table is required.

     min_keycode_return
               Returns the minimum KeyCode valid for the display.

     keysyms_per_keycode_return
          Returns the number of KeySyms stored for each KeyCode.

     keysym    Specifies the KeySym for which to search.

     keycodes_return
               Returns a list of KeyCodes that have keysym asso-
               ciated with them, or NULL if keycount_return is 0.

     keycount_return
               Returns the number of KeyCodes in the keycode
               list.

DESCRIPTION

     XtGetKeysymTable returns a pointer to the Intrinsics' copy
     of the server's KeyCode-to-KeySym table. This table must not
     be modified.

     The XtKeysymToKeycodeList procedure returns all the KeyCodes
     that have keysym in their entry for the keyboard mapping
     table associated with display. The caller should free the
     storage pointed to by keycodes_return using XtFree when it
     is no longer useful.

SEE ALSO

     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.