Re: Type-ahead searching is now hosed
Re: Type-ahead searching is now hosed
- Subject: Re: Type-ahead searching is now hosed
- From: Chris Espinosa <email@hidden>
- Date: Tue, 27 Oct 2009 23:07:51 -0700
On Oct 27, 2009, at 9:21 PM, Joar Wingfors wrote:
In 2.5, you could type 'a' and *always* expect it to scroll to and
select a1. But now in 3.2, if c2 is currently selected and you type
'a', it will scroll to and select a2. This does not make sense.
You're entitled to your opinion, but please acknowledge that this is
a matter of personal preference and not something that can be proven
true or false. Cocoa provides one behavior, you prefer another.
Xcode conforms to the system default behavior in this case. It is
certainly advantageous for us to behave in the same way as most
other apps on the system. We should have a good reason not to, and I
don't see it in this case.
Also note that AppKit behaved one way in Mac OS X 10.5 and a different
way in Mac OS X 10.6. The new behavior type-selects from the current
selection, not the top of the list. So on the one hand, it is
consistent and has its logic, but on the other hand, it is a change in
behavior.
Chris
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden