> On Apr 6, 2016, at 6:57 AM, Dave <d...@looktowindward.com> wrote: > > Yes, that’s the only way I’ve found that makes it in any way usable. It > amazes me how they change things at the drop of a hat without (so it seems) > thinking through the consequences of making such an “improvement”. I mean > really, this is simple stuff that has been working well in countless apps for > 20+ years,
Incremental search has been around since the 1980s in other popular editors like emacs. > why all of a sudden does some (not so) bright spark at Apple think that > changing the “find” operation would be a good idea, and more worryingly his > boss allow it? I love the way incremental search lets me find something with a minimal number of keystrokes. I concede that for the case discussed in this thread it’s a step back, but that honestly hadn’t occurred to me before; not sure why. I think both of you are falling into the conceptual trap of conflating your _individual_ experiences and use cases, with the general usability of a feature — i.e. “this doesn’t work for me, therefore whoever designed it is an idiot”. I’ve worked on a couple of widely used GUI apps (including Mail and iChat, in 10.0–10.5) and I know that nearly any time a feature is changed, even if 99% of users like it there will be somebody complaining that the new way is awful and everyone on the team should be fired. —Jens
_______________________________________________ Do not post admin requests to the list. They will be ignored. Xcode-users mailing list (Xcode-users@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/xcode-users/archive%40mail-archive.com This email sent to arch...@mail-archive.com
