i'm having the same problem.

i'm on a late 2008 macbook, and a clean install of b54. if i relaunch
qs and the program i'm trying to apply the custom trigger to, the
trigger will work once. after that it will stop working.

i only have two triggers set up right now, and it seems to be only
affecting the trigger tied to --> current app --> show menu items.
attempting to use this trigger has also been cuasing firefox 3 to
crash.



On Oct 21, 11:50 am, hmelman <[EMAIL PROTECTED]> wrote:
> I don't have a new MBP to try it (lucky you) but it would help to have
> more details.  Are you using QS version B54? That would be my
> recommendation. If it doesn't work try one of the later builds. Is it
> any trigger or just "particular" ones? I've had problems on my
> previous Powerbook and my current macbook pro that one key is
> recognized when setting a trigger (in my case it was cmd-v) but others
> work. Are you doing a new install or did you transfer QS settings from
> a previous machine? You might try deleting the ~/Library/Application
> Support/Quicksilver/Triggers.plist file while QS is not running and
> then recreating some triggers. There have some things that have
> corrupted that file.
>
> Howard
>
> On Oct 21, 12:12 pm, Derivatives <[EMAIL PROTECTED]> wrote:
>
> > I've read recently that this problem may infact be common but on my
> > macbook pro (late 2008 generation) custom triggers won't work. when I
> > enter a particular keyboard key and modifier combination the keyboard
> > key will not show up in the assignment window, and i just get a loud
> > beep out of the computer.
>
> > How can I fix this ?

Reply via email to