32bit (.tar.gz, 199 KB, MD5: e0c32bc91563bbccb362cad215df0b94)
32bit (uncompressed, 416 KB, MD5: 284352d0e1ffdc8f0922484412970a7f)
64bit (.tar.gz, 200 KB, MD5: 85c171b3cffdc378ff0fe947ebd246bb)
64bit (uncompressed, 427 KB, MD5: aec35a471c507083cdb14f01320db9b2)
Script to set up permissions (only required if you haven't set up permissions before)
Requires Qt. WhatPulse is built on the Qt4 library, which means that you need that (at least QtGui and QtNetwork, to be precise). If you have KDE SC 4.x (or any KDE 4.x application) installed, you already have Qt4. If you need to install Qt4 (for example on a default Ubuntu or Fedora installation), use your package manager to install the required packages. They're called "libqtgui4" and "libqt4-network" on Ubuntu; and "qt" and "qt-x11" on Fedora. On any other distro, just search for the appropriate package names, or ask us if you have problems.
File permissions. Both for ultimate reliability and enhanced cheat protection, WhatPulse gets its key/button events directly from the kernel. Usually, regular user accounts aren't allowed to read this data, which is why you have to set up permissions first.
You can either grant your user read access to /dev/input/event* yourself, or just run the provided script as root. The script will create a new group called 'input', add your user account to that group, and make the event device files readable for the group.
Open a terminal and navigate to the directory where you have downloaded the script. If you have sudo configured on your distro (e.g. Ubuntu provides this by default), just run:
$ chmod +x setup-permissions.sh $ sudo ./setup-permissions.shIf your distro uses su (e.g. Fedora), enter these commands:
$ chmod +x setup-permissions.sh $ su -c ./setup-permissions.sh
Synaptics/ALPS touchpads. By default, the drivers for these touchpads grab the event device exclusively, which means that any other program listening for device events won't see any. You can override this behaviour, how to do it depends on the version of your X server:
Section "InputClass"
Identifier "custom touchpad configuration"
MatchIsTouchpad "on"
Option "GrabEventDevice" "false"
EndSection
<merge key="input.x11_options.GrabEventDevice" type="string">false</merge>If you feel confused, have a look at this example file.
Option "GrabEventDevice" "false"
(Physical) Mouse/Finger Tracking accuracy. While on-screen cursor tracking is handled completely automatically, there is no way to automatically determine your mouse's physical DPI setting, so you need to configure this in WhatPulse's settings dialog if you want mouse tracking to be accurate.
Finger tracking on touchpads, on the other hand, uses a hard-coded default resolution which you can't change. It will work more or less accurately on most models, but the measurement won't be 100% exact, and if your touchpad happens to be somewhat weird, results might be pretty far off.
Keyboard drivers. WhatPulse is designed to work with the "evdev" keyboard driver, which is used by default if your keyboard is managed by the X server (using udev or HAL). Normally, this is the case on current distributions. If you're using an old distro, please consider upgrading. If you're managing your X.org configuration yourself, make sure your keyboard uses the "evdev" driver. Using the "kbd" driver should generally work, but might lead to problems.
Upgrading. When upgrading from an earlier version, simply replace the WhatPulse binary. There is no need to run the setup script again, and all your settings will be preserved.
Note that with version 0.95, the location for WhatPulse's configuration files changed (~/.config/whatpulse instead of ~/.whatpulse). That means that if you've been running an older version than that so far (0.8, 0.9), you should pulse before upgrading.
Distributions. This version of WhatPulse has been tested successfully on the following distributions:
Have fun using WhatPulse!
32bit (.tar.gz, 195 KB, MD5: 988f1208ac7f471de2ac52c618afcb91)
64bit (.tar.gz, 197 KB, MD5: e75f6399cc8336201048a8689171216a)
32bit (.tar.gz, 184 KB, MD5: 9a7bac8e1cdc9ae6d1769bd004c8a55d)
64bit (.tar.gz, 186 KB, MD5: da456d250528b4296bc642a1a35ebf72)
• Do not show the Geek Window when double-clicking the tray icon in order to pulse
• Fix crash when using "kbd" driver in X
• Fix a possible unjustified "Savefile has been corrupted" message
• Add context menu to Geek Window
32bit (.tar.gz, 153 KB, MD5: 3aef789af781db661ebfb01ca7ae4c28)
64bit (.tar.gz, 154 KB, MD5: d828b9da6ef6dd81e37a4fc4d0b8c01f)
Community contributed downloads:
WhatPulse forums user hostname was kind enough to provide a Package for Debian/Ubuntu/Mint 64bit (.deb, 165 KB). It contains everything you need (including the setup script) for Debian-based distributions.
Fine print: Please note that community-contributed packages are not officially supported. If installation fails, contact the creator of the package via the forums.
• Fixed auto-pulsing after x keys/clicks
• Added tooltip to tray icon
• The "About" dialog still says "Version 0.95". Oh well.
• If your X server uses the old "kbd" driver for your keyboard, some keys ("Windows", "Context Menu", "Right Arrow", "Insert", "Delete", maybe others, maybe not all of them) will cause WhatPulse to crash. Solution: upgrade your distro / reconfigure your X to use evdev/HAL.
32bit (.tar.gz, 152KB, MD5: dcadc5b5210c4ddaafa6db668d874ffe)
64bit (.tar.gz, 154KB, MD5: 4ea12eb4f440f7525cf712b5d748fb25)