but if i use command+esc to grab the contents into quicksilver it is instant, there is no delay like there is for the current selection proxy object. so if i can use applescript to perform the send to quicksilver service then it might be faster.
also, i reported the issue at the link you provided. On Oct 29, 6:27 pm, Patrick Robertson <[email protected]> wrote: > I don't think applescript will be much faster, although if it's for one > specific purpose only, then it may be. > The thing about 'current selection' is that it can deal with *any* type of > data, so it just takes a while for QS to get this information from the > frontmost app. > > > when trying to use that with textedit that only one file > > will open, is that an issue with textedit? > > I have just tried Current Selection -> Open and see that it doesn't work > properly. It must be a bug with Quicksilver. can you report it > here:https://github.com/quicksilver/Quicksilver/issues > > On 29 October 2011 10:45, yoose <[email protected]> wrote: > > > > > > > > > Thank you for the quick reply partrick. It is only with triggers that > > use the 'current selection' proxy object. Good to hear that the > > problem is being worked on. Is there an applescript that will grab the > > current selection and feed it into the first pane of quicksilver > > instead of using the current selection proxy object? will that be > > faster? I have an applescript that opens two files with diffmerge, its > > all in applescript and its pretty fast. > > > By the way, good working on getting the 'current selection' to work > > with multiple objects in B61, it has been very useful, however I > > noticed that when trying to use that with textedit that only one file > > will open, is that an issue with textedit? > > > On Oct 29, 4:02 pm, Patrick Robertson <[email protected]> > > wrote: > > > Is this just for one trigger, or all triggers that require 3rd pane > > input? > > > > If this is with the 'current selection' proxy object, then Quicksilver > > does > > > take a long time to figure out what the 'current selection' is. I am > > > planning on reducing this time in a future version, but at the moment we > > > will have to make do with waiting :( > > > > On 29 October 2011 07:52, yoose <[email protected]> wrote: > > > > > Hi, > > > > > Whenever I activate a trigger in QS it takes a long time for the QS > > > > window to pop up. Activating it normally is fast, but triggers that > > > > require an input into the third pane is painfully slow, in the range > > > > of 3+ seconds. Has anyone else had any experience with this? Is there > > > > some setting that might be causing this? I am using B61 on 10.7.2 > > > > although this happened before when i was using B60 on 10.6.8. Thank > > > > you.
