I'm fairly sure Type Text uses system scripting to get its job done,
so here's a script Action that incorporates a delay:

-- Start
using terms from application "Quicksilver"
        on process text _text
                try
                        delay 0.5
                        tell application "System Events" to keystroke _text
                on error a number b
                        tell application "Quicksilver" to activate
                        display dialog a
                        return
                end try
        end process text
end using terms from
-- End

Save in AppleScript Editor, in the folder ~/Library/Application
Support/Quicksilver/Actions/ as (for example) Type Text Delayed.
Relaunch QS, type some text in pane 1 and bring up the Action in pane
2. The 'delay' line in the script can be changed to any number (in
seconds).

On Oct 27, 10:57 pm, SilverRubicon <[email protected]> wrote:
> It does seem to be a an issue with the amount of time that the trigger
> keys are held.  I changed my trigger to work on Key Release, and if I
> type it quick enough it does in fact work.
>
> That's not an ideal solution for me so I'll continue to use Butler
> rather than QuickSilver.  QS was my first love but it's little issues
> like these in the more basic functionality that prevent me from moving
> back.  some day I hope to return to the QuickSilver fold.
>
> On Oct 27, 9:47 am, SilverRubicon <[email protected]> wrote:
>
>
>
>
>
>
>
> > Ok.  If that's the case, I'll try changing the trigger to the key
> > release.   haven't had much luck in with Type Text in any application.
>
> > On Oct 26, 6:14 pm, philostein <[email protected]> wrote:
>
> > > I think it's because as soon as the Trigger starts, you're still
> > > holding the modifier keys, causing the typed text to become keyboard
> > > shortcuts.
>
> > > Where are the snippets - QS pane 1 or clipboard, or other? Try
> > > pressing and releasing the shortcut quickly.
>
> > > On Oct 26, 11:41 pm, SilverRubicon <[email protected]> wrote:
>
> > > > I am running Quicksilver B61 (3900) on OSX 10.72.  Should triggers
> > > > with a 'Type Text' action work?  I have created a trigger to 'type'
> > > > snippets of plain text into a window.  When I activate the hotkey,
> > > > either the text is not 'typed' or the application (iterm) goes haywire
> > > > spawning dozens of windows.  Redefining the same trigger with a
> > > > 'Paste' action works flawlessly but with the side effect of modifying
> > > > the clipboard.
>
> > > > Anyone have any insight as to what is going on?  This is not the first
> > > > time I've had issues with Type Text, but I attributed it to lack of
> > > > support for 10.7.  Now that QS has been updated, the problem
> > > > continues.

Reply via email to