> On 6 Apr 2016, at 18:08, Jens Alfke <j...@mooseyard.com> wrote: > > >> On Apr 6, 2016, at 8:47 AM, Dave <d...@looktowindward.com >> <mailto:d...@looktowindward.com>> wrote: >> >> A return key is *ONE* extra keystroke and it’s a big key (on my Apple >> keyboard) so easy to hit with your little finger. I would say that at most >> it saves a 1/4 of a second having it “jump” as it does at the moment, but if >> you make a mistake it causes a LOT of wasted time having to find your place >> again rather than just hitting the delete key. > > > No, that’s not the point. It can save a lot of keystrokes! Let’s say I want > to find the next occurrence of “writeUnicodeToFile”. I press Cmd-F, W, R, … > and hey, I’m there already, no need to keep typing. Or maybe I have to press > a few more keys, depending on what text is in the file, but generally I don’t > have to type nearly the full search string. >
That’s to do with selecting “begins with” etc, nothing to do with if the command is terminated with a return or not. I’d press command+F “wr”+return, one extra keystroke…. With the jumping “feature” if you pressed Command+F “we” you’d be off who knows where, with the old-school, tried and tested method you’d just have to hit delete. >> Mail is full of bugs anyway so I’m not surprised people complained. > > (a) this was fifteen years ago and Mail was pretty awesome then. (And one of > the smartest engineering teams I’ve worked with.) Agreed that it’s gone > downhill a lot since. > (b) I’m talking about UI features, not bugs. My point exactly, these days so many useless “features" added with seemingly not much thought or design of the underlying consequences. Basically Apple engineering has gone downhill and not just on XCode. > >> It depends on what the change is but in the old days things like this were a >> preference. > > > Preferences are really problematic for UI design. Too many prefs leads to > confusion, features that most users never discover because they don’t grope > into the prefs, and trouble using someone else’s computer or explaining to > them how to do something. There’s also very often a better way to design a > feature that doesn’t need a pref. Some UX designers feel that if there has to > be a pref, the design has failed. > > (I remember that circa 2000, using IMAP mail with Mac Outlook Express > required configuring a ton of obscure prefs and account settings. I wrote up > a multi-page memo describing how to do it. With OS X Mail, even in 10.0, IMAP > Just Worked.) > > That said, Xcode is a developer tool for expert users, and already has a ton > of obscure prefs, so I could see adding one for this. (OTOH, it would require > more than two people complaining about the feature…) You can vote for it by > filing a Radar I can’t be bothered, XCode *used* to work ok, now its been “improved”. I just find away around the problem and while I’m downloading a text editor that works sanely, we can always fall back on the wonderful animations that have really improved XCode no end. Cheers Dave
_______________________________________________ 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
