Trigger Scope broken since b56a3

[Chris]

Hello,

Kudos to getting Quicksilver working under Snow Leopard, whoever you
are. I upgraded to Snow Leopard today, and it appears that
Quicksilver b56a7 (as noted elsewhere) is relatively stable and most
of the things I care about still work.

However, I've noticed that trigger scope doesn't seem to work. If I
assign a trigger to run, say, an applescript, and tell the trigger to
only be enabled in Safari, as soon as I leave the trigger pane, the
trigger is unchecked, rendering the trigger unusable.

Anyone else experience this, or know of a fix?

Thanks,
Chris

[Etienne Samson]

I have confirmed this. Scoping actually works, but there's a little
issue between stating that a trigger is active (or not) for a given
scope, and the global, enabled status (the trigger checkbox). The
scoping works because it actually disables trigger when not in the
correct scope, but it fails to reactivate them after a change (since
they are now disabled)...

I will investigate, thanks for the report !

Etienne

Le 29 août 09 à 07:35, Chris a écrit :