Lines Matching full:mouse

39 .Nd pass mouse data to the system video console driver
68 mouse operation in the text console and user programs.
69 They virtualize the mouse and provide user programs with mouse data
74 The mouse daemon listens to the specified port for mouse data,
76 The mouse daemon
83 The console driver will display the mouse pointer on the screen
84 and provide cut and paste functions if the mouse pointer is enabled
89 is opened by the user program, the console driver also passes the mouse
92 If the mouse daemon receives the signal
94 it will reopen the mouse port and reinitialize itself.
96 the mouse is attached/detached while the system is suspended.
98 If the mouse daemon receives the signal
100 it will stop passing mouse events.
103 again will resume passing mouse events.
105 interrupted by accidentally touching the mouse pad.
118 The user program which is reading mouse data
127 The DTR line may need to be dropped for a 3-button mouse
150 (in pixels) that the mouse must move before a scroll event
159 With this option set, holding the middle mouse
164 option to set the distance the mouse must move before the scrolling mode is
179 when identifying the serial mouse.
184 utility will not be able to print useful information for the serial mouse.
196 a 3-button mouse to operate in the
204 Use this option if mouse pointer slowly wanders when mouse is not moved.
211 msec (default 4000) since last real mouse movement.
215 With this option set, holding the middle mouse
219 option to set the distance the mouse must move before the scrolling mode is
230 (in pixels) that the mouse must move before the scrolling
236 Apply exponential (dynamic) acceleration to mouse movements:
237 the faster you move the mouse, the more it will be accelerated.
238 That means that small mouse movements are not accelerated,
247 your mouse hardware and your personal preference.
250 you move the mouse twice as fast, the pointer will move
273 Accelerate or decelerate the mouse input.
317 Mouse model.
336 should operate the mouse driver.
357 to communicate with the mouse.
370 Specify the protocol type of the mouse attached to the port.
376 mouse.
385 .Sx "Configuring Mouse Daemon" ) .
392 Also note that if your mouse is attached to the PS/2 mouse port, you should
397 regardless of the brand and model of the mouse.
399 mouse is attached to the bus mouse port, choose
403 Serial mouse protocols will not work with these mice.
405 For the USB mouse, the protocol must be
407 No other protocol will work with the USB mouse.
412 For the serial mouse:
415 Microsoft serial mouse protocol.
421 Mie Mouse,
428 MM Series mouse protocol.
430 Logitech mouse protocol.
459 For the bus and InPort mouse:
463 the bus and InPort mouse and should be specified for any bus mice
467 For the PS/2 mouse:
470 This is the only protocol type available for the PS/2 mouse
474 For the USB mouse,
476 is the only protocol type available for the USB mouse
517 This is useful for the mouse with two wheels of which
519 and for the mouse which has a knob or a stick which can detect
531 actually exist in this mouse, their actions will not be detected.
544 .Ss Configuring Mouse Daemon
546 of the mouse you are going to use.
547 It can be determined by looking at the connector of the mouse.
548 The serial mouse has a D-Sub female 9- or 25-pin connector.
551 The PS/2 mouse is equipped with a small, round DIN 6-pin connector.
555 remember the connector at the very end of the mouse/adapter pair is
557 The USB mouse has a flat rectangular connector.
560 The PS/2 mouse is always at
563 mouse can be attached.
567 to the mouse.
574 .Pa /dev/mouse
575 pointing to the real port to which the mouse is connected, so that you
577 .Dq mouse
580 The next step is to guess the appropriate protocol type for the mouse.
597 if the mouse driver supports this protocol type.
623 protocol regardless of the brand of the mouse.
627 protocol should always be specified for the PS/2 mouse
628 regardless of the brand of the mouse.
632 protocol for the USB mouse.
670 If the mouse has a roller or a wheel, it may be compatible with the
675 To test if the selected protocol type is correct for the given mouse,
676 enable the mouse pointer in the current virtual console,
680 start the mouse daemon in the foreground mode,
684 and see if the mouse pointer travels correctly
685 according to the mouse movement.
691 As many instances of the mouse daemon as the number of mice attached to
693 instance for each mouse.
696 mouse when s/he attaches the system to the docking station in the office.
697 Run two mouse daemons and tell the application program
702 then the application program will always see mouse data from either mouse.
703 When the serial mouse is not attached, the corresponding mouse daemon
705 program will only see mouse data coming from the daemon for the
706 PS/2 mouse.
709 the mouse pointer will travel across the screen just as if movement of
716 PS/2 mouse driver
718 virtualized mouse driver
722 USB mouse driver
735 utility determine the protocol type of the mouse at the serial port
746 utility is able to identify the protocol type of the mouse at the specified
749 option and enable the mouse pointer in the text console as above.
751 moused -p /dev/mouse -t microsoft
755 Start the mouse daemon on the serial port
756 .Pa /dev/mouse .
763 .Dl "moused -p /dev/mouse -m 1=3 -m 3=1"
770 .Dl "moused -p /dev/mouse -t intellimouse -z 4"
772 Report negative Z axis movement (i.e., mouse wheel) as the button 4 pressed
773 and positive Z axis movement (i.e., mouse wheel) as the button 5 pressed.
785 to a key in your window manager, you can suspend mouse events on your laptop if
786 you keep brushing over the mouse pad while typing.
807 for the given serial mouse.
837 are three buttons on the mouse.
843 If the mouse has only two buttons, the middle, `paste' button