Ack, I hit reply too soon.
As the FAQ says, Menu Bar triggers don't save, because QS has to get
the menu bar items on the fly—they are not permanently stored in the
QS catalogue—and so it can't keep track of these items as part of a
trigger either.
A workaround would be to create an Applescript that uses GUI scripting
to do the job, and set up a trigger to run that instead. There are two
ways to do this. If the menu item you want to run has a keyboard
shortcut assigned to it in the menus, such as ⇧⌘1, something as
simple as the following would do the job nicely:
tell application "System Events" to ¬
keystroke "1" with {command down, shift down}
If there is no keyboard shortcut assigned to the menu item, you can do
this:
tell application "system events" to ¬
click menu item "Show Top Sites" ¬
of menu "History" of menu bar 1 ¬
of application process "Safari"
This second option will briefly flash the menu at you, because it is
simulating a mouse click, but it will work.
Note that both of the options require "Enable access for assistive
devices" to be checked in the Universal Access system preference pane.
On Sep 17, 3:26 pm, "Jon Stovell (a.k.a. Sesquipedalian)"
<[email protected]> wrote:
> See point 1 of "Triggers Don't Save" on the FAQ page of this website.
>
> On Sep 16, 10:56 am, HMayes <[email protected]> wrote:
>
>
>
> > I'm using b56a7 of QS. I use abracadabra (which initially didn't work
> > in Snow Leopard but "magically" started working yesterday), and I use
> > mouse gestures to navigate in Safari, among other things. My other
> > gesture triggers are working, but any trigger involving "Menu Bar..."
> > actions ("User Interface Access +" Plugin) does not work and is gone
> > upon restarting quicksilver. I tried the "create trigger, close
> > preferences, revisit trigger pane" trick but that did not work either.
> > I know a lot of folks are having issues with Triggers under Snow
> > Leopard. Has anyone been able to get triggers involving Menu Bar
> > working? I noticed that the Menu Bar commands do work when typed into
> > the QS interface manually. Thanks
>
> > Mayes
