P.P.S.: Each of the code examples I gave should be on one line. Google's automatic formatting broke some of them up into two lines.
On Jul 26, 9:18 am, "Jon Stovell (a.k.a. Sesquipedalian)" <[email protected]> wrote: > P.S.: In my previous post, replace "jon" in /Users/jon/Library/Speech/ > Speakable Items/Application Support/Speakable Items/Quicksilver with > whatever your user name is on your Mac. > > On Jul 26, 9:14 am, "Jon Stovell (a.k.a. Sesquipedalian)" > > > > <[email protected]> wrote: > > In theory that should be pretty easy to do. > > > Since Quicksilver does almost everything via keystrokes, you might > > find it easiest to simply create a series of AppleScripts to simulate > > keystrokes, and save them in /Users/jon/Library/Speech/Speakable Items/ > > Application Speakable Items/Quicksilver. If you named each script > > after then keys to be pressed (e.g. "a.scpt" for one that types the > > letter a, or command n.scpt for one that types ⌘N), then all you would > > need to do is give say "Switch to Quicksilver" to bring up QS's > > command window, and then start dictating the keys to simulate typing. > > > These kind of AppleScripts are simple to create. For example, to > > simulate typing the letter a, the AppleScript code would be: > > > tell application "System Events" to keystroke "a" > > > To type ⌘N, the code would be: > > > tell application "System Events" to keystroke "n" using command down > > > To type ⇧⌥- (the key combination for typing an em-dash), the code > > would be: > > > tell application "System Events" to keystroke "-" using {shift down, > > option down} > > > Note that when you need to use more than one modifier key, you must > > enclose the list inside curled brackets. > > > However, to type keys like Tab or Delete, which do not create symbols, > > you need to use a slightly different form. For example, to simulate > > pressing the Tab key, use the following code: > > > tell application "System Events" to key code 48 > > > 48 is the keyboard code number for the Tab key. You can find the > > keyboard code for any key on your keyboard using a little app called > > Full Key Codes, available > > fromhttp://softwares.bajram.com/utilities/#Full_Key_Codes. > > Open that application, then press a key. In its window it will display > > various code numbers associated with what you just typed. Then one you > > are interested in is the decimal version of the keyboard code, which > > is written in blue in the lower right of the window. > > > For a final example, to press ⇧⌘Tab, you would use the following code: > > > tell application "System Events" to key code 48 using {shift down, > > command down} > > > Armed with this information, I think you will find it pretty easy to > > get Quicksilver up and running as a Speakable application. Let us know > > how well it works out for you. > > > On Jul 26, 6:21 am, synapse12 <[email protected]> wrote: > > > > Hi, > > > Has anyone had sucess with with triggering quicksilver commands using > > > the mac ox native voice recognition capabilities? I'd like to be able > > > to speak the same keystrokes that I use to control quicksilver to open > > > bookmarks and files. It seems like it should be doable, but a > > > websearch did not reveal anything too useful and I am fairly new to > > > apple scripts so I got stuck. > > > Any help is much appreciated, > > > Thanks > > > Dylan
