FastScripts Keyboard Shortcuts On Leopard

November 28th, 2007

It has been brought to my attention that some users are experiencing a bug with FastScripts on Leopard, where keyboard shortcuts just seem to “stop working.” Unfortunately when this happens, there are no helpful clues in the console, and the application seems to need to be quit and relaunched for shortcuts to start firing again.

I use FastScripts constantly and, truth be told, I did see this behavior in an earlier Leopard beta seed. But since the GM 10.5 and 10.5.1 releases, I have yet to see this problem even once.

I’m hoping to get some feedback from other users who have been running FastScripts on Leopard, and might have possibly seen this behavior. Please let me know if you have any ideas about what might be provoking it. Whether certain scripts might cause it to start happen, etc.

Finally, if you recognize this kind of faulty behavior, perhaps something you’ve seen in another application that supports global shortcuts, I’d be interested in hearing about it. Basically, I’m interesting in any clues that you can provide to help me figure out what might be going wrong here.

Thanks!

3 Responses to “FastScripts Keyboard Shortcuts On Leopard”

  1. Kevin Ballard Says:

    I don’t use FastScripts, but I know that launching World of Warcraft will, for no apparent reason, disable my Lookup In Dictionary, Toggle Zoom Smoothing, Dashboard, and Exposé keyboard shortcuts, necessitating a trip to the Mouse & Keyboard prefpane.

  2. Luis de la Rosa Says:

    People have reported that sometimes WebnoteHappy shortcuts don’t work in Leopard. I wrote up a workaround. Hopefully we can track down the cause.

  3. Dylan Smith Says:

    Unfortunately, I don’t use FastScripts, but I have discovered a really annoying Finder bug where, if you rename a folder to a package (that’s the best way I know to describe the operation of renaming folder “testdir” to e.g.”testdir.tmBundle”) all keyboard interaction with the Finder stops working. There is a particular Finder error that shows up in Console, but I don’t have it in front of me now. Feel free to email if you think it might shed light.

Comments are Closed.

Follow the Conversation

Stay up-to-date by subscribing to the Comments RSS Feed for this entry.