For any question, comment, concern, or, most importantly bug not mentioned here, don't hesitate to email me at and ask me a question.

Known Incompatibilities

xGestures is incompatible with the following software in Mac OS X 10.3:

  • Some Kensington Mice and Wacom Tablets will not work. The way the drivers for these particular products work unfortunately prohibits xGestures from being able to receive mouse events. Concerning Kensington Mice, users have reported that xGestures won't respond to the upper mouse buttons (i.e. buttons 3 and up), though the left and right buttons still function as normal.
  • xGestures is currently entirely compatible with the following software: DoubleCommand, Sidetrack, USB Overdrive. (In USB Overdrive, be sure to set the gesturing mouse button to "click nth button" where n is the number of that button.)
  • xGestures is partially compatible with uControl. The features of uControl that affect the mouse currently do not work, but all other functions of uControl do work. If you want the functionality of both xGestures and uControl, consider getting Sidetrack, which is by the same author of uControl, provides the same functionality (and more), and is compatible with xGestures.

xGestures should be completely compatible with all of the above hardware in software in Mac OS X 10.4. As of version 1.4, I'm not aware of any incompatibilities, but should any come up, feel free to email me and I'll try to fix it.

Some possible problems that might come up, but hopefully won't:

  • (NEW) I want to copy part or all of my xGestures configuration to another computer or user account.

    Right now, there's no feature in the program to do this, but I'm going to add one soon. In the meantime, you can copy the what.xGestures.plist file located in /Library/Preferences/ to another computer or user account to copy all of your xGestures settings.
  • Visual feedback doesn't work on my second monitor.

    I've been trying to fix this, but I don't actually own a second monitor so it's been difficult. I think it might work as it should now, as of version 1.6. Then again, maybe not. If it doesn't work expect me to continue trying to fix this.
  • The Volume and Eject gesture actions don't work on my Intel Mac.

    This bug should hopefully be fixed as of version 1.7. If not, let me know and I'll try again.
  • Sometimes the gesture gets "stuck" after I finish gesturing, and I have to move the mouse a little bit in order for the gesture action (or context menu) to happen.

    I think I fixed this in version 1.7, but I can't be too sure without extensive testing and feedback because this bug happens really inconsistently. (At least for me.) If it's still happening for you, let me know and I'll keep working on it.
  • Something goes wrong when I remote control my computer using either VNC or synergy while xGestures is running.

    As of version 1.4, xGestures ought to be compatible with programs like synergy or VNC, but I later realized it was still buggy. As of version 1.5, a lot of those bugs have been fixed, and as far as I know right now, you can remote control a computer with VNC or synergy, and even gesture while doing so, and it should work fine. However, it's not out of the question that there's still a bug. If there is, quitting xGestures will almost certainly resolve the issue. Email me with what happened and I'll try to fix it.
  • I tried doing a gesture in a dialog or sheet that was supposed to press a button, but it didn't work.

    Every now and then, though usually this is pretty rare, a dialog or a sheet will be recognizable as such, but won't have any way for another program (say xGestures) to see what dialog buttons are in its dialog box and then try to click them. Usually this is made possible using Apple's accessibility API, but sometimes it breaks and then there's no way to click the buttons. As a last ditch effort xGestures will try to send a return or command-period keystroke so that something (anything) will happen, but sometimes that doesn't work either. So far, I personally haven't encountered a dialog box that xGestures couldn't click the buttons on, but I'm sure there's still some out there in the wild, just waiting to annoy someone. Worst case scenario, you'll have to move the cursor to the buttons and click them the old fashioned way.
  • I deleted the Finder from my applications list, and I can't get it to come back!

    You can re-add the Finder by clicking the '+' button and browsing to System:Library:Core Services:Finder. However, as of version 1.1, you can't remove the Finder anymore, so hopefully this won't ever come up.
  • I set a gesture to pick a menu item, and it's not working!

    Make sure you typed in the menu item exactly as it is on the menu itself, capitalization and everything. If it contains an elipses character, be sure to try both three periods and the actual elipses character, typed by holding option and pressing semicolon.
  • I typed in the menu item exactly, and it still doesn't work
    - or -
    I can't minimize, close, or zoom a window using xGestures
    These actions require that the 'Enable Access For Assistive Devices' in the Universal Access control panel be enabled. To turn it on, go into the Universal Access control panel and click the 'Enable Access for Assistive Devices' button at the bottom of the page.
  • I have uControl, DoubleCommand, or another program that uses an HID-based kernel extension to modify how OS X works, now it and/or xGestures doesn't work

    The following is true only in Mac OS X 10.3:
    As of version 1.1, xGestures is compatible with DoubleCommand and at least partially compatible with uControl. Any aspect of uControl that modifies the mouse's behavior (namely the scroll wheel emulation and left-handed mouse feature) won't work. However, these features and more are also available in SideTrack, which is fully compatible with xGestures. (However, it is not free.)

    These programs should be fully compatible with xGestures in Mac OS X 10.4.
  • xGestures suddenly crashed and/or my mouse doesn't work anymore

    Either try restarting your computer, or relaunch xGestures and then quit it again. If you've suddenly lost usage of one of your mouse buttons, you can probably regain it by holding modifiers keys down, as holding modifiers other than the ones picked in the preferences pane will disable gestures. Also, xGestures isn't supposed to crash. Email me to report the bug.
  • My xGestures serial number didn't work for some reason

    Oops, that shouldn't happen, but if it does, it's probably my fault. Email me and I'll try to get you fixed up as soon as I can.

  • I have a Kensington Mouse or a Wacom Tablet, and xGestures isn't working

    Currently, as of version 1.4, in Mac OS X 10.3, xGestures doesn't work with Wacom tablets, and partially doesn't work with Kensington mice. The problem lies in the way the drivers for these devices send messages to the system, and how xGestures retrieves messages from the system. The only solution I can suggest as of now is to uninstall the driver and use either the default OS X driver or USB Overdrive (which I believe works okay). However, this solution isn't very good because a lot of the functionality of these products are lost when removing the driver.

    In Mac OS X 10.4, xGestures 1.4 uses a different method for retrieving mouse input and consequently should work fine with Wacom tablets and pretty much any mouse. If this is not the case, let me know and I'll try to fix it.
  • This shouldn't ever happen, but I'm suddenly getting kernel panics now!

    Firstly, this should only be applicable in Mac OS X 10.3, because xGestures doesn't use a kernel extension anymore for Mac OS X 10.4. But holy hell, that shouldn't ever happen! If you want to temporarily disable the kernel extension and not uninstall xGestures, though, start your computer without extensions by holding down the shift key as it boots, and then go into /Library/StartupItems/ and move the folder 'xGestures' into some other folder. This will prevent the kernel extension from loading at startup. A more permanent solution is to uninstall xGestures entirely.

    If you are using Mac OS X 10.4 and, somehow, xGestures manages to directly or indirectly cause a kernel panic, you should definitely let me know too. But since there's no kernel extension, and xGestures isn't messing around with the kernel at all, there really is no way for this to happen that I can think of.

    Also, if this happens, email me immediately and let me know your full computer specifications, which version of OS X you're running, and possibly any other information that might be relevent, like what you were doing immediately before the kernel panic happened.