Hi, It does not work at all on my macbook pro for the 'function' (fn) key. I'm on leopard and build 3815 worked just fine?
I also reverted to that version on my macpro since it does apeare now when pressing the key for a longer time and that's really bad. I have it on ctrl and can not type control-c in the terminal anymore... Bert On Sep 26, 12:53 pm, Etienne Samson <[EMAIL PROTECTED]> wrote: > Replying on-list for the record ;-) > > Le 24 sept. 08 à 14:42, ATMB a écrit : > > > > > Etienne Samson ha scritto: > > >> Hi Quicksilver fans ! > > >> There's a new build available > >> athttp://code.google.com/p/blacktree-alchemy/downloads/list > > > I have this problem: > > > I always used one press of the "command" key to invoke Quicksilver, > > and as of b55a4 there's a problem: > > > BEFORE b55a4, quicksilver appeared AFTER I released the modifier key > > (so, a quick "press+release" of command in my case), so I could use > > all command+key shortcuts (e.g. command+W, command+Q, command+TAB...) > > without invoking quicksilver. > > > IN b55a4, quicksilver appears in the moment I press the modifier key, > > making it useless for other shortcuts. > > > I reverted to b55a3, and I hope this "regression" gets fixed asap... : > > ( > > I tried to change the setting (invoke qs on DOUBLE modifier key > > press... but I don't like it. two presses are simple and safe, ok... > > but I liked SO much the old way....) > > Hey, forgot this one too ;-). > I tried to fixmodifier-onlyactivation (which was utterly broken on > Leopard, because it only worked if QS was the front app), but although > it now works even if QS isn't the front app, it will register > modifiers EVEN if they are used for shortcuts (like pressing Cmd-C/Cmd- > V quickly with Cmd set as a double-modifier). I'll try to finish the > fix, but I thought it would be better to merge themodifier-only > activation feature inside triggers (since they are pretty much doing > the same thing, and would allow for even more powerful triggers ;-)). > > Apologies to those of you that usemodifier-onlyactivation > extensively, I will fix this ASAP.
