I don't suppose that there is a fix pending for this? How I miss my Current Application > Show Menu Items! It was my favorite productivity accelerator on my Mac!!!
On Jan 22, 4:25 pm, Mike <[EMAIL PROTECTED]> wrote: > +1 > > I used to use the Current Application > Show Menu Items trigger all > the time, but no dice in Leopard. > > I see the same behavior as posted above. Seems to work once after > reboot, then not again. Errors in Console Log similar to those as > above: > "1/10/08 01:06:49 Quicksilver[23482] *** -[NSCFType boolValue]: > unrecognized selector sent to instance 0x15a473b0 > 1/10/08 01:06:49 Quicksilver[23482] HIToolbox: ignoring exception > '*** -[NSCFType boolValue]: unrecognized selector sent to instance > 0x15a473b0' that raised inside Carbon event dispatch " > > Mike > > On Jan 10, 6:30 pm, rawchicken <[EMAIL PROTECTED]> wrote:> I have the same > problem. I remember reading a thread on the old > > forums that said that the menu items feature doesn't work properly > > inLeopardand there is no fix at the moment. > > > On Jan 10, 1:43 pm, jcdurivage <[EMAIL PROTECTED]> wrote: > > > > Sorry, I misunderstood what you were asking. The first pane is > > > Current Application, the second is show menu items, and the third is > > > blank. > > > > Jason > > > > On Jan 10, 10:00 am, Howard Melman <[EMAIL PROTECTED]> wrote: > > > > > When I asked what the trigger was, I didn't mean the key, I meant the > > > > command, that is what is in each of the 3 panes. Give me (or someone > > > > else as I'm still on Tiger) enough information to try to recreate > > > > your problems. > > > > > Howard > > > > > On Jan 10, 2008, at 11:52 AM, Jorge Chao wrote: > > > > > > I've been having similar problems withproxyobjects since I upgraded > > > > > toLeopard. I have my trigger set to ctrl-space. It seems to work for > > > > > some apps (Terminal.app for example), do absolutely nothing for > > > > > others(Safari), and use a TON of processor time for others (Mail.app > > > > > is one of these). The inconsistency of behavior is what's most > > > > > confusing to me. > > > > > > Just thought I'd chime in, I thinkproxyobjects are the bees knees > > > > > and getting them to work onLeopard(if they are in fact broken) would > > > > > be awesome. > > > > > > On Jan 10, 2:10 am, jcdurivage <[EMAIL PROTECTED]> wrote: > > > > >> After playing with it some, I realized that I think I had the trigger > > > > >> defined wrong. After "fixing" the problem, these are the errors that > > > > >> I was getting from Console.app > > > > > >> Jason > > > > > >> 1/10/08 01:06:49 Quicksilver[23482] *** -[NSCFType boolValue]: > > > > >> unrecognized selector sent to instance 0x15a473b0 > > > > >> 1/10/08 01:06:49 Quicksilver[23482] HIToolbox: ignoring exception > > > > >> '*** -[NSCFType boolValue]: unrecognized selector sent to instance > > > > >> 0x15a473b0' that raised inside Carbon event dispatch > > > > > >> On Jan 10, 12:26 am, jcdurivage <[EMAIL PROTECTED]> wrote: > > > > > >>> Hi Howard, > > > > > >>> Thanks for your help. The trigger that I have defined is option > > > > >>> +space. Nothing happens to the program when it fails, it just > > > > >>> doesn't > > > > >>> pull up the Quicksilver window. The error that I seem to be getting > > > > >>> from the Console.app is: An error occurred while scanning "User > > > > >>> Accounts": launch path not accessible. I have the access enabled > > > > >>> for > > > > >>> assistive devices turned on. > > > > > >>> On Jan 9, 7:59 pm, Howard Melman <[EMAIL PROTECTED]> wrote: > > > > > >>>> On Jan 9, 2008, at 9:13 PM, jcdurivage wrote: > > > > > >>>>> One of the things that I found most useful about Quicksilver > > > > >>>>> was to > > > > >>>>> use the Current Applicationproxyso as not have to use the > > > > >>>>> trackpad > > > > >>>>> to get to menu items. I had it set up as a hotkey (⌥ + Space). > > > > >>>>> Ever > > > > >>>>> sinceLeopard, it doesn't seem to work. I can get the hotkey to > > > > >>>>> invoke one time after I start up Quicksilver but after that, it > > > > >>>>> doesn't work. I even tried changing it to a new hotkey and that > > > > >>>>> didn't seem to help. I was wondering if any of you were having > > > > >>>>> the > > > > >>>>> same issue. I'm on a MBP running 10.5.1 and Quicksilver β54. > > > > >>>>> Thanks > > > > >>>>> in advance for any help or advice. > > > > > >>>> What trigger have you defined? > > > > >>>> What happens when it fails? > > > > >>>> Are there any errors in Console.app? > > > > >>>> Do you have Enable access for assistive devices enabled in > > > > >>>> Universal > > > > >>>> Access system prefs? > > > > > >>>> Howard
