> > The easiest thing to do would be to add a delay in your trigger setup. > > This would give you time to release the modifier keys before the > > action starts.
Works like a charm. Thanks. --Benton On Oct 2, 10:59 am, Chris Cairns <[EMAIL PROTECTED]> wrote: > also, you can take advantage of this behavior....one simple example > would be: > > i take random notes so that i can paste them in forums as my queries. > whenever i do that i write the subject (i.e. topic heading) and then > hit "tab" so that when i do "type text" the subject gets inserted in > the subject field and the remaining text in the text field. > There can be many other uses of this behavior if u choose to explore it. > > On 02-Oct-08, at 8:40 PM, praetorian wrote: > > > > >> so I made a shortcut for it: ctrl-opt-cmd-v. > > > As Chris pointed out the keystrokes from QS are indistinguishable from > > the ones from the keyboard. > > If you have your trigger set to activate on release QS will wait until > > you release the v key but not the modifier keys. > > The target application will see the keystrokes coming from QS and the > > modifier keys you are still holding. > > It will interpret it as a series of ctrl-opt-cmd shortcuts. > > > The easiest thing to do would be to add a delay in your trigger setup. > > This would give you time to release the modifier keys before the > > action starts.
