Boundless gratitude on behalf of the mac community to the QS developers for making this helpful app available to us.
SUMMARY When pasting from the QS clipboard history into an app indirectly via a TextExpander form fill-in, QS ignores the fill-in and pastes directly to the app. MATERIALS USED: MacBook Pro 17", early 2008 6 GB RAM Mac OS 10.9.1 Quicksilver 1.1.3 TextExpander 4.1.1 THE PROBLEM I have TextExpander snippets that use single-line field fill-ins. I use them to create boiler-text with optional fill-ins. When I click "OK" in one of these snippets, TextExpander dumps the full text of it into the foreground app. When I paste into one of these snippets from the QS clipboard, the paste should appear in the snippet and stay there until I finish the snippet and click "OK". Sometimes it works correctly but often the paste falls through the field directly into the app behind it, even though I have not clicked away from the TE snippet window. This never happens if I paste without using QS' clipboard history. THE USUAL SUSPECT According to Brian at TextExpander <[email protected]> (who uses QS too, himself): "I can affirm that the problem is actually Quicksilver. "What is happening is that Quicksilver is setting the pasteboard to the desired contents from the history, then posting a Command-V event. This is very similar to what TextExpander does when it expands a snippet. The key point is that Mac applications have two choices when posting "virtually typed" keyboard events: A - post the event to a specific process (application), or B - post a generic "un-targeted" event. "Quicksilver is posting the event using option A, and they are targeting the application which owns the menu bar. In most cases this is a sensible thing to do, but as you may have noticed, the fill-in window does _not_ switch the menu bar to 'TextExpander Helper' -- it remains as 'Firefox' or 'TextEdit' or whatever. "I don't know if this is the kind of bug that the Quicksilver folks would want to invest time in fixing, or not, because it is subtle, and they may have some timing issues. That is, the Quicksilver application may be the text focus app at the time the Command-V event gets posted, but of course you don't want the Command-V to be directed to Quicksilver, you want it to go to the app behind. This is, of course, one of the main reasons they are 'targeting' the event as they do. "A lot of work has been invested in TextExpander around similar issues. That is, I've spent long days chasing down similarly subtle issues, and they are not fun. Quicksilver is developed/maintained by volunteers, so… "In the meantime, I would work around it by: - just using "plain old" Command-V if the desired text is already on the clipboard - using Command-Option-V in the Save window's field FIRST to get the desired clipboard history item "moved to the front", then Command-A to Select All, then "ts\", then Command-V to get the desired effect (ie. replacing all the file name text with your snippet -- hope that make sense!)" I use the QS all the time. It is one of the essential things in my software. -- You received this message because you are subscribed to the Google Groups "Quicksilver" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/blacktree-quicksilver. For more options, visit https://groups.google.com/groups/opt_out.
