On Apr 20, 2011, at 4:17 PM, dsanson wrote: > This is probably obvious, but when activated, QS often already has > something in the first pane---the result of the previous action. This > might be a document that I recently opened or an application that I > recently launched or a phone number that I recently looked up and > copied to the clipboard or displayed in large text. Sometimes I want > to perform some new action on this thing; sometimes I want to arrow > away from it (into it, or to one of its neighbors, or to its parent > folder, etc.); but most often, I want to start a completely new > search. So this seems like a case where the first pane has been > populated by some previous activity, but I would not want the second > pane to be active by default.
The first pane would always be active when you invoke Quicksilver. (Whether it’s the normal keystroke, or ⌘⎋.) We’re only talking about when you run an action that brings the interface back immediately. > Also, the current behavior feels "consistent" to me (but that may just > be the result of habit), and I worry that the proposed behavior would > not feel as consistent. I don't want to have to pay attention to the > details of how I got where I am, and I don't want to have to look > before knowing whether hitting tab is going to move me from the first > pane to the second or the second to the first... Yeah, the more I think about it, it should probably be a preference. I think the new way (if implemented) will clearly be better, but years of muscle memory can’t be ignored. -- Rob McBroom <http://www.skurfer.com/>
