Don’t switch to text mode when browsing

[skurfer]

If you have the option “Switch to text mode when no match is found” enabled, a small typo when navigating deep into something can force you to start all over.

This preference should only be active when the interface is first called up. Using → or / should disable it until Quicksilver is dismissed and brought back up.

[pjrobertson]

Just out of interest - how useful is the "switch to text" option?

I don't think we'd have grounds for removing it completely - it may annoy quite a few veteran users - but it's just a thought.

I have no objections to this feature request.

You probably want to look in QSSearchObjectView.m there's a bool called isBrowsing or something similar. You'll want the insertSpace: method in that file to do nothing if isBrowsing is false.

^^ I've just been working in that file, so I thought I'd share what I knew with you

[skurfer]

Just out of interest - how useful is the "switch to text" option?

I don't think we'd have grounds for removing it completely - it may annoy quite a few veteran users - but it's just a thought.

Very useful (to me anyway). You can just start typing without thinking about which mode you’re in. I wasn’t suggesting removing it.

But the use case for it really only applies when you first invoke Quicksilver (to enter a URL or some search terms or some text to be sent to an action). Once you start browsing, you’re obviously looking for something that exists and not interested in entering a free-form string.

^^ I've just been working in that file, so I thought I'd share what I knew with you

Thanks.