Triggers not working under Snow Leopard

[Oliver Langner]

Dear all,

I first thought, I'm too dumb to use triggers, but got them working
easily on my work mac that is still running Leopard.

I installed the latest version of quicksilver (β56a7) on my home mac
(with snow leopard). I also tried to reinstall everything after
removing all settings files etc. (like proposed in the faq). I observe
mainly two issues:

1. all the predefined triggers normally appearing in earlier builds of
quicksilver are gone (no itunes triggers at all)

2. whatever trigger I define, I only get a system beep or no response
at all (although the same definition of triggers works perfectly on my
Leopard mac).

Any suggestions?
Oliver

[Oliver Langner]

Just to update:

I rolled back via TimeMachine to the old version I had installed
(β54). And yep, the preferences window does not work as already
reported, but all triggers work perfectly. So, to me seems to be a bug
in the latest version.

Oliver

[ujal]

Try to deactivate and activate the trigger. Works for me, though i
have another problem: qs will not save the triggers after restarting
qs :(

[switters]

Hi folks,

I'm in a similar position. I could not get b56a7 to work no matter
what I did, so I rolled back to b54. All of the triggers I set up in
Leopard still work perfectly. However, as Oliver mentioned the
Preferences screen is blank with b54 so I won't be able to make any
changes.

Is there anyone who has got triggers to work with b56a7?

[roschtatoschta]

Yes, triggers are working for me with b56a7, using the steps described
in this thread:
http://groups.google.com/group/blacktree-quicksilver/browse_thread/thread/bb17c30eeb2d40e8/120a2063e9ebe201?lnk=gst&q=roschtatoschta#120a2063e9ebe201

For me, one important step was to install the plugins again manually
from within QS and not simply copying the old plugins folder into ~/
Library/Application Support/Quicksilver .

For the triggers, I was able to simply copy the old triggers folder
into the new ~/Library/Application Support/Quicksilver.

Only thing bugging me right now is that "Large Type" does not work
properly. And that stupid dock icon/spaces issue. :(

Regards,

Carsten

[Christoffer Winterkvist]

I got triggers working under SL with β56a7 (3825)
I just removed all my prefs and plugins and began to setup QS from
scratch...
that seemed to have done the trick.

Mvh Christoffer Winterkvist
---------------------------------------
op...@noodlemantra.eu

[switters]

Thank you. I've got everything working now with b56a7. Triggers are
faster than in b54. Now have to reinstall the plugins.

On Sep 8, 8:09 am, Christoffer Winterkvist <op...@noodlemantra.eu>
wrote:

[switters]

Looks like I spoke too soon. While it's true that the triggers I set
up under Leopard are working with b56a7/SL, I have not been able to
set up any new triggers. No matter what keyboard shortcuts I choose,
none of them work. Have any of you been able to set up NEW triggers
with b56a7/SL?

[roschtatoschta]

You are right, only my old triggers work. When I create a new one,
nothing happens when I try to invoke it. :(

[ujal]

For all the people having trouble to setup new trigger-shortcuts there
is a solution but only till qs restarts(at least for me): deactivate
(checkbox) and activate the trigger again after the shortcut is set.

[switters]

Yep, that works. Thanks. Guess I'll need to keep QS running as much
as possible (which I pretty much do already - I only restart or shut
down for maintenance purposes). Hope there's a fix soon. I love my
triggers!

[Christoffer Winterkvist]

I got the Trigger to stick by doing the following routine...
Open Triggers ...
Add the one you want ...
Close the QS prefs window and the open Triggers ... (again)
Then if I restart QS my new triggers seem to stick.

Hopes this helps...

Mvh Christoffer Winterkvist
---------------------------------------
op...@noodlemantra.eu

[switters]

Thanks Christopher, that's very helpful.

The only triggers I'm having problems with now are the built-in
"Command Window in Text Mode" and "Command Window with Selection". I
can get something to happen with Command Window with Selection, but it
doesn't do what it's supposed to do. For example, let's say I have a
folder selected in finder and I invoke the keystroke for Command
Window with Selection. The QS window does open, but not with the
selection.

I can't get the Command Window with Text to work at all. I click the
checkbox to activate it, choose the keyboard shortcut, then close the
Preferences window of QS, quit QS, and restart it. When I invoke the
shortcut I get an error sound from the System. Nothing happens with
QS.

Can anyone verify if these triggers are working for you?

[switters]

Following up on my last post, if I invoke QS and then use Command-G, I
can get it to load the selection from the Finder. However, it will
not load selections from any other applications. For example, I
select some text in Safari, invoke QS, hit Command-G. Nothing
happens.

I have enabled Advanced Features in Application Preferences and I have
also selected "Pull Selection from Front Application Instead of
Finder" in the Extras Preferences menu. Still doesn't work.

[Christoffer Winterkvist]

I use the 'Send to Quicksilver' service to accomplish this.
Not quite as good and does not work in all applications but... it's
worth a try.
You just bind it to the key you want under System Preferences >
Keyboard > Keyboard Shortcuts > Services >Pictures

Mvh Christoffer Winterkvist
---------------------------------------
op...@noodlemantra.eu

[switters]

Christopher,

When I attempt to install the "Services Menu" plugin in QS b56a7, QS
crashes after installation and each time upon attempting to reopen.
If I remove the Services plugin, QS is fine. How did you get it to
work?

Chris

On Sep 10, 10:19 am, Christoffer Winterkvist <op...@noodlemantra.eu>
wrote:

[Christoffer Winterkvist]

I don't now :/
It has always been there, I guess I installed it when I was on leopard
or something...
Maybe there is a way to install it manually?

Mvh Christoffer Winterkvist
---------------------------------------
op...@noodlemantra.eu

[switters]

Okay, I guess you don't need to install the QS services menu after
all. I got it working just using the steps you described. They
keyboard shortcut I chose doesn't work in all applications, though.
Do you have any suggestions for a "safe" shortcut? Thanks again.

[andreb]

On Leopard if you look into the global Services menu you will find a
Quicksilver sub menu there which contains two entries (greyed out):

1. Get Current Selection (Internal)
2. Send to Quicksilver

The first one has by default Cmd+Esc as global shortcut.
I'd guess that this is what's used to power the Quicksilver advanced
setting "Pull selection from front application instead of Finder".
Which makes it work that you can just select text in any app and hit
Cmd+Esc and have QS appear in text mode with the selectedt text.

On Snow Leopard those entries are absent.
And that's even if Quicksilver is a normal dock-icon bearing front app
and even if all service entries are enabled on the new Services prefs
page which can be found inside the keyboard prefs from System
Preferences.

I tried to debug the Info.plist part of the missing QS' service menu
entries (services are registered with the system by means of
specifying it in the app's Info.plist file) by comparing it with Quick
Search Box's Info.plist (QSB's service entry does show up unlike QS')
but so far have not been able to get QS' needed services to register.

Which means all that's working for now on SL should be pulling the
selection from the Finder.

Cheers

André

[andreb]

Seems what did the trick in getting QS' services to register was to
delete all Quicksilver.app bundles which also have an Info.plist
inside them that specifies the same service. I guess the rule here is
that if Spotlight can't find the Quicksilver.app bundle it's not
visible to the Services registry.

Once I had deleted all instances of Quicksilver.app (and their
Info.plists) inside and then restarted my SL system I was able to find
two new services in System Preferences which when ticked where
available globally.
The good news is that it will also work when QS does not have a dock
icon.
Once I did all that I can now get any selection (text or otherwise)
into QS again by hitting Cmd+Esc.

HTH

André

[andreb]

Quick correction:

Once I had deleted all instances

should read:

Once I had deleted all >other< instances

[Christoffer Winterkvist]

I followed your instructions and now I have both Send to quicksilver
and Get Current Selections... thanks for the info :)

Mvh Christoffer Winterkvist
---------------------------------------
op...@noodlemantra.eu

[jepo]

I guess I'm having a similar problem, though I don't think quite the
same. I can get many triggers to work, including gesture triggers, but
no matter what I do, none of my mouse triggers will work. I've tried
assigning with every modifier key to every side of the screen,
checking/unchecking, restarting and activating, doing the hokey
pokey.. and nothing! Anybody else having this problem? It seems
limited to only the mouse triggers since both gestures and hotkey
triggers work fine.

[switters]

What you suggested also works for me. Command-Esc now pulls
selections into QS. However, I first had to disable the Front Row
keyboard shortcut which was by default configured to Command-Esc.
Luckily I don't use Front Row at all so that's no big loss.

Thanks again!

[adamrice]

So far, I've been having mixed success with getting triggers to work.
Opening defaults.plist and setting useeffects to false and deleting
the existing triggers.plist file seemed to help, somewhat. I can now
create some triggers, but not others.

For example: I have created a trigger to open an app. That works. I
have created another trigger to bring up Google in my web browser.
That doesn't. I variously get the following results:
1. The trigger works until I relaunch Quicksilver. After that there's
an empty trigger where it used to be in my triggers list
2. Nothing happens
3. My Mac beeps, but nothing else happens.

[adamrice]

To follow up on that, I've created a dead-simple applescript
"OpenGoogle.scpt" and set up a trigger "Open Google | Run", which does
work. The script is as follows

tell application "Safari"
open location "http://google.com/"
activate -- brings Safari to front
end tell

[Dan Shockley]

I was having trouble getting hot keys to work for the iTunes Next Song
(and Previous Song) scripts. I wanted to use command-control-
RightArrow (or LeftArrow) for them. First unusual thing: the arrow-key
didn't show an arrow, but rather the "missing Unicode" glyph. Also, I
could not get those HotKeys to work, depsite closing and reopening the
Triggers window, as someone suggested. All that would hapen when I
tried to use them was a beep. HOWEVER, when I changed the HotKeys to
Control-Option-RightArrow and Control-Option-LeftArrow, they
functioned correctly, despite the strange glyph used to represent the
arrow keys in the HotKey box.

Dan


On Sep 6, 6:08 am, Oliver Langner <o.lang...@gmx.net> wrote:
> Dear all,
>
> I first thought, I'm too dumb to usetriggers, but got them working
> easily on my work mac that is still running Leopard.
>
> I installed the latest version of quicksilver (β56a7) on my home mac
> (with snow leopard). I also tried to reinstall everything after
> removing all settings files etc. (like proposed in the faq). I observe
> mainly two issues:
>
> 1. all the predefinedtriggersnormally appearing in earlier builds of
> quicksilver are gone (no itunestriggersat all)
>
> 2. whatever trigger I define, I only get a system beep or no response
> at all (although the same definition oftriggersworks perfectly on my
> Leopard mac).
>
> Any suggestions?
> Oliver

[Zippy]

I also have mixed success with triggers.
Here is some info for the Quicksilver developers that I hope will help
them fix the triggers bug.
Case 1 works, case 2 fails:

1. I can create a new trigger that opens a text file that lives on my
Desktop "Open filename.txt", it is saved to triggers and stays there
on subsequent Quicksilver relaunches.

2. However, when I create a new trigger that opens a text file in the /
Applications subpath "Open filename2.txt" it works until I relaunch
Quicksilver, and then the trigger entry shows up as "Open (null)" and
does not respond to the trigger.

After case 2, I inspected the ~Library/Application Support/Quicksilver/
Triggers.plist entries and verified the "/Applications/filename2.txt"
path string exists in the command/directID of one of the entries. For
some reason it is not getting read back in correctly or used correctly
by Quicksilver since it lives in the /Applications directory. As I
stated, a file that lives on the Desktop is treated correctly on
relaunch.

Thanks for taking a look at it!

[pendolino]

this worked for me! thanks. note that i did not have to relaunch
quicksilver. just a toggle of and on seemed to work. also note that
function keys such as F1, F2 that i use for a number of triggers work
but will not appear correctly in the trigger preferences. instead they
are replaced with some funky looking character.



On Sep 10, 1:28 am, Christoffer Winterkvist <op...@noodlemantra.eu>
wrote:

[cawpin]

I am experiencing a similar problem. I had a trigger set up to search
Google (CMD+G) under Leopard. It would send the query qss-http://
www.google.com/search?q=*** and open the results in my default
browser, which happens to be Firefox. Upon upgrading to SL this
trigger resets to the mentioned "Open (null)" and the trigger no
longer does anything. This happens whenever QS is closed and re-
opened, including rebooting. I have another trigger to launch a
Terminal (CMD+ALT+T) window which still works perfectly. However, no
matter what keyboard shortcut I assign to the Google search action,
the action is wiped out on a restart of QS. Personally, I think this
may be a bug in the Web Search plugin.

[vivian]

I don't think it's the Web Search plugin; this seems to happen with
any web address triggers that aren't recognized. I have a trigger for
Google Maps that is recognized and is listed as "Open Google Maps,"
and that one works even after reboot. But any of my triggers that are
listed as "Open http..." stop working after reboot, including
calendar.google.com, docs.google.com, and www.weatherunderground.com.

So something weird is going on with the processing of http:// I
guess.

On Oct 28, 7:45 pm, cawpin <caw...@gmail.com> wrote:
> I am experiencing a similar problem. I had a trigger set up to search

> Google (CMD+G) under Leopard. It would send the query qss-http://www.google.com/search?q=***and open the results in my default