Yes. But you need to customize X client programs. See Colas Nahaboo's web page (http://www.inria.fr/koala/colas/mouse-wheel-scroll/) . The imwheel program works by translating mouse button 4 and mouse button 5 events into key events. Thus, you have to get the mouse driver to translate mouse wheel events to button 4 and 5 events. There are two ways of doing this, the first way is to have moused(8) do the translation. The second way is for the X server itself to do the event translation.

The answer is, unfortunately, ''It depends''. These mice with additional features require specialized driver in most cases. Unless the mouse device driver or the user program has specific support for the mouse, it will act just like a standard two, or three button mouse.

Yes! Schedule-HR will work with a wheel mouse; just make sure you install the software that was provided with your mouse.

Support for the Microsoft Intellimouse is enabled in our X Windows setup by default; however, you must configure a few extra options in your ~/.Xdefaults file in order to get it to work with some applications (such as Netscape). You can find the text to be added on the Colas Nahaboo X mouse wheel scroll page. Simply copy the text for the application program(s) you require, paste it into your ~/.

If you are using the default console driver, syscons, you can use a mouse pointer in text consoles to cut & paste text. Run the mouse daemon, moused, and turn on the mouse pointer in the virtual console: # moused -p /dev/xxxx -t yyyy # vidcontrol -m on Where xxxx is the mouse device name and yyyy is a protocol type for the mouse. See the moused(8) man page for supported protocol types. You may wish to run the mouse daemon automatically when the system starts. In version 2.2.

This seems to be caused by a bug in Internet Explorer. The only solution I have found is to not use the mouse wheel.

The short answer is you can't. A deliberate design decision has been made to not introduce system hooks that can affect the reliability and responsiveness of both VirtuaWin and your computer. So VirtuaWin has no built in mouse wheel support.

Many models used these pins with round bails for securing the wheels to the axels. By moving the pins the machine could be made to freewheel. By moving one pin the machine could be rendered one wheel drive for easier handling in light duty. Many machines included this click pin feature. In this picture the pin passes through the wheel and the axle causing power to be transmitted.

To date, there’s no “genuine” mouse wheel support in Geogrid products. Operation of the mouse wheel is purely coincidental, depending on the mouse driver installed. The next version of Geogrid (e.g. in the Top50 Version 5) will include scrolling with the mouse wheel and the “hand symbol” for moving the map.

In most cases you only need to add Option ''ZAxisMapping'' ''4 5'' to the InputDevice section of your XF86Config. If that does not do the trick, try this6link for more resources and instructions. You upgraded to XFree 4.3.0 or higher. Run fc-cache as root to (re)build the font cache, and things should be fine. I'd recommend getting the latest self-installing driver package from http://www.nvidia.com and read the official README thoroughly as most problems are handled in it.

Assuming the server and the server software application supports the scroll wheel, all you have to do is to change one line in the thinstation.conf:

Make sure you're using the proper protocol for your mouse, most of the new optical mice use the "IMPS/2" protocol. As defined by your xorg.conf's InputDevice section. The instructions for the next answer won't work if the proper protocol isn't being used. If you're using XFree86 version 4.x, or X.Org at all, put this in your /etc/X11/xorg.conf (or XF86Config): It's pretty simple. Change your mouse configuration section in XF86Config or xorg.

In X, a scroll wheel counts as three buttons - up is one, down is another. Clicking the wheel is a third button. You then just need to add these two lines under the mouse section (usually 'Identifier "Mouse1"' or something similar). For a 7 button mouse, you also need to create the file /etc/X11/xinit/.Xmodmap and put the following in it for the wheel to be mapped onto the right buttons:

This is a known bug in Tk that prevents this on Windows. The obvious Tk code causes a hard crash in the Python dll: it's the only time Leo has taken such a hard crash. The UniversalScrolling plugin is an attempt at a workaround. Scrolling with the mouse wheel may be possible on Linux. See the code in createTkTreeCanvas in leoTkinterFrame.py

If you are using syscons (the default console driver), you can configure FreeBSD to support a mouse pointer on each virtual screen. In order to avoid conflicting with X, syscons supports a virtual device called /dev/sysmouse. All mouse events received from the real mouse device are written to the sysmouse device via moused. If you wish to use your mouse on one or more virtual consoles, and use X, see Q: 4.13. and set up moused.

If you are running a post-2.2.5 version of FreeBSD, the necessary driver, psm, is included and enabled in the kernel. The kernel should detect your PS/2 mouse at boot time. If you are running a previous but relatively recent version of FreeBSD (2.1.x or better) then you can simply enable it in the kernel configuration menu at installation time, otherwise later with -c at the boot: prompt. It is disabled by default, so you will need to enable it explicitly.