X-Git-Url: http://ncurses.scripts.mit.edu/?p=ncurses.git;a=blobdiff_plain;f=man%2Fcurs_mouse.3x;fp=man%2Fcurs_mouse.3x;h=19795ca7151bf7be50c84a193464ffbd7e2afd02;hp=c18be3fa3378ed4eebd1bcde57fca5f6d8cebad9;hb=74433bcf4f6fe40862a28f3c00edaedcd5054b01;hpb=e6bb3226cdd35f5fd9f45bb1685cc2203c889480 diff --git a/man/curs_mouse.3x b/man/curs_mouse.3x index c18be3fa..19795ca7 100644 --- a/man/curs_mouse.3x +++ b/man/curs_mouse.3x @@ -1,6 +1,6 @@ '\" t .\"*************************************************************************** -.\" Copyright 2018-2019,2020 Thomas E. Dickey * +.\" Copyright 2018-2020,2021 Thomas E. Dickey * .\" Copyright 1998-2015,2017 Free Software Foundation, Inc. * .\" * .\" Permission is hereby granted, free of charge, to any person obtaining a * @@ -28,7 +28,7 @@ .\" authorization. * .\"*************************************************************************** .\" -.\" $Id: curs_mouse.3x,v 1.53 2020/10/17 23:25:08 tom Exp $ +.\" $Id: curs_mouse.3x,v 1.57 2021/12/25 21:49:32 tom Exp $ .ie \n(.g .ds `` \(lq .el .ds `` `` .ie \n(.g .ds '' \(rq @@ -55,51 +55,51 @@ .na .hy 0 .SH NAME -\fBhas_mouse\fR, -\fBgetmouse\fR, \fBungetmouse\fR, -\fBmousemask\fR, \fBwenclose\fR, -\fBmouse_trafo\fR, \fBwmouse_trafo\fR, -\fBmouseinterval\fR \- mouse interface through curses +\fBhas_mouse\fP, +\fBgetmouse\fP, \fBungetmouse\fP, +\fBmousemask\fP, \fBwenclose\fP, +\fBmouse_trafo\fP, \fBwmouse_trafo\fP, +\fBmouseinterval\fP \- mouse interface through curses .ad .hy .SH SYNOPSIS -\fB#include \fR +\fB#include \fP .PP -\fBtypedef unsigned long mmask_t;\fR +\fBtypedef unsigned long mmask_t;\fP .PP .nf -\fBtypedef struct {\fR -\fB short id; \fR\fI/* ID to distinguish multiple devices */\fR -\fB int x, y, z; \fR\fI/* event coordinates */\fR -\fB mmask_t bstate; \fR\fI/* button state bits */\fR -\fB} MEVENT;\fR +\fBtypedef struct {\fP +\fB short id; \fP\fI/* ID to distinguish multiple devices */\fP +\fB int x, y, z; \fP\fI/* event coordinates */\fP +\fB mmask_t bstate; \fP\fI/* button state bits */\fP +\fB} MEVENT;\fP .fi .PP -\fBbool has_mouse(void);\fR +\fBbool has_mouse(void);\fP .sp -\fBint getmouse(MEVENT *\fP\fIevent\fP\fB);\fR +\fBint getmouse(MEVENT *\fP\fIevent\fP\fB);\fP .br -\fBint ungetmouse(MEVENT *\fP\fIevent\fP\fB);\fR +\fBint ungetmouse(MEVENT *\fP\fIevent\fP\fB);\fP .sp -\fBmmask_t mousemask(mmask_t \fP\fInewmask\fP\fB, mmask_t *\fP\fIoldmask\fP\fB);\fR +\fBmmask_t mousemask(mmask_t \fP\fInewmask\fP\fB, mmask_t *\fP\fIoldmask\fP\fB);\fP .sp -\fBbool wenclose(const WINDOW *\fP\fIwin\fP\fB, int \fP\fIy\fP\fB, int \fP\fIx\fP\fB);\fR +\fBbool wenclose(const WINDOW *\fP\fIwin\fP\fB, int \fP\fIy\fP\fB, int \fP\fIx\fP\fB);\fP .sp -\fBbool mouse_trafo(int* \fP\fIpY\fP\fB, int* \fP\fIpX\fP\fB, bool \fP\fIto_screen\fP\fB);\fR +\fBbool mouse_trafo(int* \fP\fIpY\fP\fB, int* \fP\fIpX\fP\fB, bool \fP\fIto_screen\fP\fB);\fP .br -\fBbool wmouse_trafo(const WINDOW* \fP\fIwin\fP\fB,\fR - \fBint* \fP\fIpY\fP\fB, int* \fP\fIpX\fP\fB, bool \fP\fIto_screen\fP\fB);\fR +\fBbool wmouse_trafo(const WINDOW* \fP\fIwin\fP\fB,\fP + \fBint* \fP\fIpY\fP\fB, int* \fP\fIpX\fP\fB, bool \fP\fIto_screen\fP\fB);\fP .sp -\fBint mouseinterval(int \fP\fIerval\fP\fB);\fR +\fBint mouseinterval(int \fP\fIerval\fP\fB);\fP .br .SH DESCRIPTION These functions provide an interface to mouse events from -\fBncurses\fR(3X). -Mouse events are represented by \fBKEY_MOUSE\fR -pseudo-key values in the \fBwgetch\fR(3X) input stream. +\fBncurses\fP(3X). +Mouse events are represented by \fBKEY_MOUSE\fP +pseudo-key values in the \fBwgetch\fP(3X) input stream. .SS mousemask .PP -To make mouse events visible, use the \fBmousemask\fR function. +To make mouse events visible, use the \fBmousemask\fP function. This will set the mouse events to be reported. By default, no mouse events are reported. @@ -120,7 +120,7 @@ Here are the mouse event type masks which may be defined: l l _ _ l l. -\fIName\fR \fIDescription\fR +\fBName\fP \fBDescription\fP BUTTON1_PRESSED mouse button 1 down BUTTON1_RELEASED mouse button 1 up BUTTON1_CLICKED mouse button 1 clicked @@ -161,13 +161,13 @@ _ .SS getmouse .PP Once a class of mouse events has been made visible in a window, -calling the \fBwgetch\fR function on that window may return -\fBKEY_MOUSE\fR as an indicator that a mouse event has been queued. +calling the \fBwgetch\fP function on that window may return +\fBKEY_MOUSE\fP as an indicator that a mouse event has been queued. To read the event data and pop the event off the queue, call -\fBgetmouse\fR. -This function will return \fBOK\fR if a mouse event -is actually visible in the given window, \fBERR\fR otherwise. -When \fBgetmouse\fR returns \fBOK\fR, the data deposited as y and +\fBgetmouse\fP. +This function will return \fBOK\fP if a mouse event +is actually visible in the given window, \fBERR\fP otherwise. +When \fBgetmouse\fP returns \fBOK\fP, the data deposited as y and x in the event structure coordinates will be screen-relative character-cell coordinates. The returned state mask will have exactly one bit set to @@ -177,62 +177,62 @@ A subsequent call to \fBgetmouse\fP will retrieve the next older item from the queue. .SS ungetmouse .PP -The \fBungetmouse\fR function behaves analogously to \fBungetch\fR. +The \fBungetmouse\fP function behaves analogously to \fBungetch\fP. It pushes -a \fBKEY_MOUSE\fR event onto the input queue, and associates with that event +a \fBKEY_MOUSE\fP event onto the input queue, and associates with that event the given state data and screen-relative character-cell coordinates. .SS wenclose .PP -The \fBwenclose\fR function tests whether a given pair of screen-relative +The \fBwenclose\fP function tests whether a given pair of screen-relative character-cell coordinates is enclosed by a given window, returning \fBTRUE\fP if it is and \fBFALSE\fP otherwise. It is useful for determining what subset of the screen windows enclose the location of a mouse event. .SS wmouse_trafo .PP -The \fBwmouse_trafo\fR function transforms a given pair of coordinates +The \fBwmouse_trafo\fP function transforms a given pair of coordinates from stdscr-relative coordinates to coordinates relative to the given window or vice versa. The resulting stdscr-relative coordinates are not always identical to window-relative coordinates due to the mechanism to reserve lines on top or bottom of the screen for other purposes -(see the \fBripoffline\fP and \fBslk_init\fR(3X) calls, for example). +(see the \fBripoffline\fP and \fBslk_init\fP(3X) calls, for example). .bP -If the parameter \fBto_screen\fR is \fBTRUE\fR, the pointers -\fBpY, pX\fR must reference the coordinates of a location -inside the window \fBwin\fR. +If the parameter \fIto_screen\fP is \fBTRUE\fP, the pointers +\fIpY, pX\fP must reference the coordinates of a location +inside the window \fIwin\fP. They are converted to window-relative coordinates and returned through the pointers. -If the conversion was successful, the function returns \fBTRUE\fR. +If the conversion was successful, the function returns \fBTRUE\fP. .bP If one of the parameters was NULL or the location is -not inside the window, \fBFALSE\fR is returned. +not inside the window, \fBFALSE\fP is returned. .bP -If \fBto_screen\fR is -\fBFALSE\fR, the pointers \fBpY, pX\fR must reference window-relative +If \fIto_screen\fP is +\fBFALSE\fP, the pointers \fIpY, pX\fP must reference window-relative coordinates. They are converted to stdscr-relative coordinates if the -window \fBwin\fR encloses this point. -In this case the function returns \fBTRUE\fR. +window \fIwin\fP encloses this point. +In this case the function returns \fBTRUE\fP. .bP If one of the parameters is NULL or the point is not inside the -window, \fBFALSE\fR is returned. +window, \fBFALSE\fP is returned. The referenced coordinates are only replaced by the converted coordinates if the transformation was successful. .SS mouse_trafo .PP -The \fBmouse_trafo\fR function performs the same translation -as \fBwmouse_trafo\fR, -using stdscr for \fBwin\fR. +The \fBmouse_trafo\fP function performs the same translation +as \fBwmouse_trafo\fP, +using stdscr for \fIwin\fP. .SS mouseinterval .PP -The \fBmouseinterval\fR function sets the maximum time (in thousands of a +The \fBmouseinterval\fP function sets the maximum time (in thousands of a second) that can elapse between press and release events for them to be recognized as a click. -Use \fBmouseinterval(0)\fR to disable click resolution. +Use \fBmouseinterval(0)\fP to disable click resolution. This function returns the previous interval value. -Use \fBmouseinterval(\-1)\fR to obtain the interval without altering it. +Use \fBmouseinterval(\-1)\fP to obtain the interval without altering it. The default is one sixth of a second. .SS has_mouse .PP @@ -241,11 +241,11 @@ successfully initialized. .PP Note that mouse events will be ignored when input is in cooked mode, and will cause an error beep when cooked mode is being simulated in a window by a -function such as \fBgetstr\fR that expects a linefeed for input-loop +function such as \fBgetstr\fP that expects a linefeed for input-loop termination. .SH RETURN VALUE -\fBgetmouse\fR and \fBungetmouse\fR -return the integer \fBERR\fR upon failure or \fBOK\fR +\fBgetmouse\fP and \fBungetmouse\fP +return the integer \fBERR\fP upon failure or \fBOK\fP upon successful completion: .RS 3 .TP 5 @@ -261,22 +261,22 @@ It also returns an error if no more events remain in the queue. returns an error if the FIFO is full. .RE .PP -\fBmousemask\fR +\fBmousemask\fP returns the mask of reportable events. .PP -\fBmouseinterval\fR +\fBmouseinterval\fP returns the previous interval value, unless the terminal was not initialized. In that case, it returns the maximum interval value (166). .PP -\fBwenclose\fR and \fBwmouse_trafo\fR -are boolean functions returning \fBTRUE\fR or \fBFALSE\fR depending +\fBwenclose\fP and \fBwmouse_trafo\fP +are boolean functions returning \fBTRUE\fP or \fBFALSE\fP depending on their test result. .SH PORTABILITY -These calls were designed for \fBncurses\fR(3X), and are not found in SVr4 +These calls were designed for \fBncurses\fP(3X), and are not found in SVr4 curses, 4.4BSD curses, or any other previous version of curses. .PP -SVr4 curses had support for the mouse in a variant of \fBxterm\fP. +SVr4 curses had support for the mouse in a variant of \fBxterm\fP(1). It is mentioned in a few places, but with no supporting documentation: .bP the \*(``libcurses\*('' manual page lists functions for this feature @@ -322,11 +322,11 @@ PDCurses, however, does not use video terminals, making it unnecessary to be concerned about compatibility with the escape sequences. .PP -The feature macro \fBNCURSES_MOUSE_VERSION\fR is provided so the preprocessor +The feature macro \fBNCURSES_MOUSE_VERSION\fP is provided so the preprocessor can be used to test whether these features are present. -If the interface is changed, the value of \fBNCURSES_MOUSE_VERSION\fR will be +If the interface is changed, the value of \fBNCURSES_MOUSE_VERSION\fP will be incremented. -These values for \fBNCURSES_MOUSE_VERSION\fR may be +These values for \fBNCURSES_MOUSE_VERSION\fP may be specified when configuring ncurses: .RS 3 .TP 3 @@ -340,10 +340,10 @@ removes the definitions for reserved events. The mask uses 29 bits. .RE .PP -The order of the \fBMEVENT\fR structure members is not guaranteed. +The order of the \fBMEVENT\fP structure members is not guaranteed. Additional fields may be added to the structure in the future. .PP -Under \fBncurses\fR(3X), these calls are implemented using either +Under \fBncurses\fP(3X), these calls are implemented using either xterm's built-in mouse-tracking API or platform-specific drivers including .RS 3 @@ -357,13 +357,13 @@ OS/2 EMX .PP If you are using an unsupported configuration, mouse events will not be visible to -\fBncurses\fR(3X) (and the \fBmousemask\fR function will always -return \fB0\fR). +\fBncurses\fP(3X) (and the \fBmousemask\fP function will always +return \fB0\fP). .PP -If the terminfo entry contains a \fBXM\fR string, +If the terminfo entry contains a \fBXM\fP string, this is used in the xterm mouse driver to control the way the terminal is initialized for mouse operation. -The default, if \fBXM\fR is not found, +The default, if \fBXM\fP is not found, corresponds to private mode 1000 of xterm: .PP .RS 3 @@ -388,21 +388,21 @@ wheel/scrolling mice send position reports as a sequence of presses of buttons 4 or 5 without matching button-releases. .SH BUGS Mouse events under xterm will not in fact be ignored during cooked mode, -if they have been enabled by \fBmousemask\fR. +if they have been enabled by \fBmousemask\fP. Instead, the xterm mouse report sequence will appear in the string read. .PP Mouse events under xterm will not be detected correctly in a window with its keypad bit off, since they are interpreted as a variety of function key. -Your terminfo description should have \fBkmous\fR set to \*(``\\E[M\*('' +Your terminfo description should have \fBkmous\fP set to \*(``\\E[M\*('' (the beginning of the response from xterm for mouse clicks). -Other values for \fBkmous\fR are permitted, +Other values for \fBkmous\fP are permitted, but under the same assumption, i.e., it is the beginning of the response. .PP Because there are no standard terminal responses that would serve to identify -terminals which support the xterm mouse protocol, \fBncurses\fR assumes that -if \fBkmous\fR is defined in the terminal description, +terminals which support the xterm mouse protocol, \fBncurses\fP assumes that +if \fBkmous\fP is defined in the terminal description, or if the terminal description's primary name or aliases contain the string \*(``xterm\*('', then the terminal may send mouse events. @@ -410,7 +410,7 @@ The \fBkmous\fP capability is checked first, allowing the use of newer xterm mouse protocols such as xterm's private mode 1006. .SH SEE ALSO -\fBcurses\fR(3X), -\fBcurs_kernel\fR(3X), -\fBcurs_slk\fR(3X), -\fBcurs_variables\fR(3X). +\fBcurses\fP(3X), +\fBcurs_kernel\fP(3X), +\fBcurs_slk\fP(3X), +\fBcurs_variables\fP(3X).