[ale] dual mice under X ?!?!
Darrell Golliher
darrell at golliher.net
Fri Jun 29 09:52:55 EDT 2001
On Fri, Jun 29, 2001 at 09:33:51AM -0400, Christopher Bergeron wrote:
> Does anyone have any idea how to implement dual mice under X? I've got an
> application that requires both a wireless mouse and a touchscreen panel.
> The touchscreen plugs into the serial port and just acts like a mouse. The
> mouse plugs into the ps2 port and acts like a mouse.
>
> Has anyone ever seen this done before?!? or heard of how it can be done?
>
>
>
I have my laptop setup so that I can use both my touchpad and an
external USB mouse at the same time. My xconfig
follows.. (improvements on it are welcome!)
-darrell
# File generated by anaconda.
Section "ServerLayout"
Identifier "Anaconda Configured"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Mouse1" "SendCoreEvents"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection
Section "Files"
# The location of the RGB database. Note, this is the name of the
# file minus the extension (like ".txt" or ".db"). There is normally
# no need to change the default.
RgbPath "/usr/X11R6/lib/X11/rgb"
# Multiple FontPath entries are allowed (they are concatenated together)
# By default, Red Hat 6.0 and later now use a font server independent of
# the X server to render fonts.
FontPath "/usr/X11R6/lib/X11/fonts/TrueType"
FontPath "unix/:7100"
EndSection
Section "Module"
Load "GLcore"
Load "dbe"
Load "dri"
Load "extmod"
Load "fbdevhw"
Load "pex5"
Load "glx"
Load "pex5"
Load "record"
Load "xie"
Load "freetype"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "keyboard"
# Option "AutoRepeat" "500 5"
# when using XQUEUE, comment out the above line, and uncomment the
# following line
# Option "Protocol" "Xqueue"
# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
# Option "Xleds" "1 2 3"
# To disable the XKEYBOARD extension, uncomment XkbDisable.
# Option "XkbDisable"
# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults). For example, for a non-U.S.
# keyboard, you will probably want to use:
# Option "XkbModel" "pc102"
# If you have a US Microsoft Natural keyboard, you can use:
# Option "XkbModel" "microsoft"
#
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
# Option "XkbLayout" "de"
# or:
# Option "XkbLayout" "de"
# Option "XkbVariant" "nodeadkeys"
#
# If you'd like to switch the positions of your capslock and
# control keys, use:
# Option "XkbOptions" "ctrl:nocaps"
Option "XkbRules" "xfree86"
Option "XkbModel" "pc101"
Option "XkbLayout" "us"
Option "XkbVariant" ""
Option "XkbOptions" ""
EndSection
Section "InputDevice"
Identifier "Mouse0"
# Modified by mouseconfig
Driver "mouse"
Option "Device" "/dev/psaux"
Option "Protocol" "PS/2"
Option "Emulate3Buttons" "yes"
# Option "ZAxisMapping" "4 5"
EndSection
Section "InputDevice"
Identifier "Mouse1"
# Modified by mouseconfig
Driver "mouse"
Option "Device" "/dev/input/mice"
Option "Protocol" "IMPS/2"
Option "ZAxisMapping" "4 5"
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "Monitor Vendor"
ModelName "Monitor Model"
HorizSync 30-60
VertRefresh 60-90
EndSection
Section "Device"
# no known options
Identifier "ATI Rage 128 Mobility"
Driver "r128"
VendorName "ATI Rage 128 Mobility"
BoardName "ATI Rage 128 Mobility"
#BusID
EndSection
Section "Screen"
Identifier "Screen0"
Device "ATI Rage 128 Mobility"
Monitor "Monitor0"
DefaultDepth 16
Subsection "Display"
Depth 16
Modes "1024x768" "800x600" "640x480"
EndSubsection
Subsection "Display"
Depth 24
Modes "1024x768" "800x600"
EndSubsection
Subsection "Display"
Depth 8
Modes "1024x768" "800x600"
EndSubsection
EndSection
Section "DRI"
Mode 0666
EndSection
--
To unsubscribe: mail majordomo at ale.org with "unsubscribe ale" in message body.
More information about the Ale
mailing list