Problems with Proxies (Leopard)

[jcdurivage]

One of the things that I found most useful about Quicksilver was to
use the Current Application proxy so as not have to use the trackpad
to get to menu items. I had it set up as a hotkey (⌥ + Space). Ever
since Leopard, 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.

Cheers,

Jason

[Howard Melman]

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

[jcdurivage]

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.

[jcdurivage]

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

[Jorge Chao]

I've been having similar problems with proxy objects since I upgraded
to Leopard. 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 think proxy objects are the bees knees
and getting them to work on Leopard (if they are in fact broken) would
be awesome.

[Howard Melman]

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

[jcdurivage]

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

[rawchicken]

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 in
Leopard and there is no fix at the moment.

[Mike]

+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 <Peter.L.Stu...@gmail.com> 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 <jcduriv...@gmail.com> 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 <hmel...@gmail.com> 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

> > > >>>>> 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

[nontoppo]

I also remember reading this was a known regression in Leopard on the
old forum.

All you can hope for is that Ankur fixes it in his branch:

http://lipidity.com/software/quicksilver/

[wildgunman]

Does anyone know if someone is actively working on this issue?
Everyone reports the same problem but no one seems to know what to do
about it short of downgrading to Tiger.

Does anyone have any idea why it happens either? The console log
doesn't make much sense to me. Of course I'm not that well versed in
the OS mechanics.

Regardless, the main question is, does anyone know if this issue is
being worked on by anyone? If they are, I'd be happy to lend my
admittedly meager skills.

[seyDoggy]

Same issue here. The only dev I know actively working on the QS
framework we all know and love is Ankur from lipidity.com. Alcor
(blacktree.com) is still working on components of QS but on what
sounds like an all new, future framework that is possibly app
independent... but don't quote me on that.

So... with that said... GO ANKUR GO!

[wildgunman]

I experienced the same problem from day one of Leopard. I hate to say
this, but I eventually remapped the key I used to use for the proxy to
the spotlight help menu, which does essentially the same thing. I'm
not proud...

[arth...@gmail.com]

how did you set it to that? that could solve a big chunk of my leopard
& quicksilver woes.

[wildgunman]

Oh, sorry. I didn't see that this thread continued.

Go to the system preferences --> Keyboard & Mouse --> Keyboard
Shortcuts

Third from the top is "Show Help Menu" I think the hotkey is
automatically assigned to Command-?

This is tough because you have to hit shift and the tree keys are all
bunched up next to each other.

Map it to Option-Space, like most people do with their invoke proxy
command in QS. Then the command will automatically bring up the help
search bar which always displays an active command for the toolbar
first, before it lists help topics. Now you have a makeshift
Quicksilver button.

My keyboard map is as follows:
Command-Space: Invoke Quicksliver
Option-Space: Invoke Help Menu
Ctrl-Space: Invoke Spotlight

I know some people have actually replaced QS with Spotlight, but I
just can't see it. QS is still more powerful and intuitive, even if
it is sadly losing ground. If that spotlight plugin would just work
more intuitively, maybe I could have the best of both worlds.

[George]

Snazzy. Thanks for the update. I haven't made it all the way through
Howard's user guide, but this would be a good addition. The last time
I saw a note of his though he was running Tiger where this isn't
broken.

[Evan David Light]

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!!!

[Martin Hauser]

I'm not quite sure what's causing the problem on your end... here for
me it works fine.
Though I have recently redone my whole quicksilver setup purging my
whole configuration, redownloading the latest quicksilver from
blacktree and... well, proxy stuff and that 'current application ->
show menu items' works reliable no matter how often I try. I'm running
10.5.2 by the way.

[Gandalf]

Well, I tried that too and no such luck. I'm still having problems.
I'm running b54 (3815) and 10.5.2 and I can't get "Show Menu Items" or
"Show Menu" or "Menu Bar" or "Menu Bar Items" to work. I mean,
they're there in the catalog and everything, but they don't do
anything. The list of menu items is empty. I tried purging
everything I could think of--the QS folder in my library and
everything. Nothing works.

On Feb 28, 5:13 am, Martin Hauser <grummle...@googlemail.com> wrote:
> I'm not quite sure what's causing the problem on your end... here for
> me it works fine.
> Though I have recently redone my whole quicksilver setup purging my
> whole configuration, redownloading the latest quicksilver from
> blacktree and... well, proxy stuff and that 'current application ->

> showmenuitems' works reliable no matter how often I try. I'm running

> 10.5.2 by the way.
>
> Evan David Light wrote:
> > I don't suppose that there is a fix pending for this? How I miss my

> > Current Application > ShowMenuItems! It was my favorite