Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'Find - Replace, not really a bug but a bad implementation' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Find - Replace, not really a bug but a bad implementation
Authored by: hamarkus on Jan 25, '05 03:17:33PM

I agree with Allan in that the way find/replace works in Cocoa is not a bug but a 'feature', however, its implementation is misleading to say the least.

For once, after hitting command-F the 'Replace' and 'Replace & Find' buttons probably should be grayed out and the 'Next' button be called 'Find' since if nothing is selected (or since nothing is found yet, and thereby nothing selected) there is nothing to replace (yet) and hitting the blue button actually finds something.

And after you, or the find command, has selected something it is not really intuative to select the menu command 'Find' to replace it (although one quickly learns that I guess, like learning to shut Windows by selecting 'Start').



[ Reply to This | # ]
Find - Replace, not really a bug but a bad implementation
Authored by: robg on Jan 25, '05 04:46:31PM

That was my point -- it really *shouldn't* work that way. Gray out "Replace & Find" until after "Find" has been used.

It also doesn't make much sense that, even if you are using "Replace and Find" in the right way by Finding first, that it keeps replacing *after* you've found all occurrences.

Bug or feature is a minor quibble; it clearly shouldn't work this way! :)

-rob.



[ Reply to This | # ]