X-Git-Url: http://ncurses.scripts.mit.edu/?p=ncurses.git;a=blobdiff_plain;f=doc%2Fhtml%2Fman%2Fcurs_mouse.3x.html;h=240f615daee7f8d66cd03b6af40413d55aa7ce0d;hp=296d50fd699e8e8adc7c1ac0fe7aba672e183d89;hb=3d46d7e9d3e210417f34acf3b469378558398d07;hpb=06078d3fa68db669ed37178c01873546b4b28745 diff --git a/doc/html/man/curs_mouse.3x.html b/doc/html/man/curs_mouse.3x.html index 296d50fd..240f615d 100644 --- a/doc/html/man/curs_mouse.3x.html +++ b/doc/html/man/curs_mouse.3x.html @@ -1,7 +1,8 @@ - - + curs_mouse 3x - + @@ -63,13 +64,18 @@ } MEVENT; bool has_mouse(void); + int getmouse(MEVENT *event); int ungetmouse(MEVENT *event); + mmask_t mousemask(mmask_t newmask, mmask_t *oldmask); + bool wenclose(const WINDOW *win, int y, int x); + bool mouse_trafo(int* pY, int* pX, bool to_screen); - bool wmouse_trafo(const WINDOW* win, int* pY, int* pX, - bool to_screen); + bool wmouse_trafo(const WINDOW* win, + int* pY, int* pX, bool to_screen); + int mouseinterval(int erval); @@ -106,12 +112,12 @@ BUTTON2_PRESSED mouse button 2 down BUTTON2_RELEASED mouse button 2 up BUTTON2_CLICKED mouse button 2 clicked + BUTTON2_DOUBLE_CLICKED mouse button 2 double clicked BUTTON2_TRIPLE_CLICKED mouse button 2 triple clicked --------------------------------------------------------------------- BUTTON3_PRESSED mouse button 3 down BUTTON3_RELEASED mouse button 3 up - BUTTON3_CLICKED mouse button 3 clicked BUTTON3_DOUBLE_CLICKED mouse button 3 double clicked BUTTON3_TRIPLE_CLICKED mouse button 3 triple clicked @@ -319,6 +325,10 @@ \E[?1000%?%p1%{1}%=%th%el%; + The mouse driver also recognizes a newer xterm private mode 1006, e.g., + + \E[?1006;1000%?%p1%{1}%=%th%el%; + The z member in the event structure is not presently used. It is in- tended for use with touch screens (which may be pressure-sensitive) or with 3D-mice/trackballs/power gloves. @@ -343,9 +353,11 @@ Because there are no standard terminal responses that would serve to identify terminals which support the xterm mouse protocol, ncurses as- - sumes that if your $TERM environment variable contains "xterm", or - kmous is defined in the terminal description, then the terminal may - send mouse events. + sumes that if kmous 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. The kmous capability + is checked first, allowing the use of newer xterm mouse protocols such + as xterm's private mode 1006.

SEE ALSO