4 ms·
You know what would be an awesome Xcode UI improvement? A Find feature that isn't completely broken. Back in Xcode 3.0 (I think), Apple replaced the old single
by aaronbrethorst 16y ago
You know what would be an awesome Xcode UI improvement? A Find feature that isn't completely broken.
Back in Xcode 3.0 (I think), Apple replaced the old single-file Find dialog (i.e. Cmd-F) with one of those newer style inline search bars (like what you see when you do an in-page search in Safari or Firefox).
Great in theory, and completely broken in practicality.
Setup: Create a UIViewController, go to the implementation file, scroll to the bottom, insert your cursor.
- Wrap-around search only works intermittently: Search for initWithNibName. It will tell you at least one match exists, but it won't show it. Hit Cmd-G to try to make it wrap around. It might work, it might not. Who knows?! Weirdly, I found just now that if I switch over to the header file (by pressing Cmd-Option-Up Arrow) and then switch back that wrap-around search magically starts working.
- Case-insensitive search only works intermittently: search for initwithnibname. It will, most likely, tell you that no matches were found.
- Single-file find and replace requires me to take my hands off the keyboard. It is not possible (at least by default) to enable single-file find and replace without moving the mouse cursor to the drop down on the left side of the Find 'strip' and choosing Find & Replace from the menu.
- teaspoon 16y agoNot to mention that locating the search-in-selection feature is now tantamount to discovering an easter egg. I had to google it.
- aaronbrethorst 16y agoI had NO idea that existed. Care to share the trick?
- teaspoon 16y agoHold the option key and see which button changes!
- conover 16y agoThe find feature in Textmate is the same way. I'm not sure how that became prevalent. It's really difficult to notice if you are new to an application.
- mortenjorck 16y agoYeah, that's always been a bit of a usability problem. Hidden gestures are really just the new "hold a random modifier key and watch what happens!"
- deleted 16y ago[deleted]
- sshumaker 16y agoReally, Apple just needs to release their plugin documentation - and some of these problems could actually be fixed by developers who have to fight them every day.
- Zev 16y agoFWIW, If you use the key commands, the first and third issues are avoidable -- though, I have run into all of the issues when using the mouse. There's a key combo for that opening the find and replace menu; ctrl + cmd + c. Then you can tab through. Hitting enter will "replace and find next", shift + enter will "replace and find previous." By default, there aren't any explicit key combinations for specifically replacing the selected text / replace all / replace and find {next, previous}. But, you can set them in Xcode's preferences, under the Key Bindings tab (in the Edit -> Find subtree). I hijacked cmd + r (from "run") for "replace and find", shift + cmd + r is used for "replace all".
- aaronbrethorst 16y agoI run into #1 all the time without using the mouse. I do my best to never take my hands off the keyboard when i'm in my editor or IDE.