By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
454,692 Members | 1,246 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 454,692 IT Pros & Developers. It's quick & easy.

replace oddity

P: n/a
guy
why if i do a select on ablock of text (in vs2003) when i do a find/replace
is find next and replace disabled? replace all is there but i may well not
want to do that?
if i pick any of the other 'search' options replace and find next are enabled.
why?

guy
Nov 21 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
Good Question.

I suspect the logic was that instances of the item you want to replace
should be searched for whever they are with an option to selectively
replace. Whereas it would make less sense ( or may do ) and is less likely
to be a requirement to only replace this within the selection. Nevertheless,
you do have a point, perhaps they should have made this optional. I suspect
it's a concious design feature. !

--
Terry Burns
http://TrainingOn.net

"guy" <gu*@discussions.microsoft.com> wrote in message
news:E7**********************************@microsof t.com...
why if i do a select on ablock of text (in vs2003) when i do a
find/replace
is find next and replace disabled? replace all is there but i may well not
want to do that?
if i pick any of the other 'search' options replace and find next are
enabled.
why?

guy

Nov 21 '05 #2

P: n/a
guy
glad you agree - at least a bit!
its a real pain when you want to replace dr in your selection with
theDataReader or whatever and it mangles drawing and drat too!
guy

"Terry Burns" wrote:
Good Question.

I suspect the logic was that instances of the item you want to replace
should be searched for whever they are with an option to selectively
replace. Whereas it would make less sense ( or may do ) and is less likely
to be a requirement to only replace this within the selection. Nevertheless,
you do have a point, perhaps they should have made this optional. I suspect
it's a concious design feature. !

--
Terry Burns
http://TrainingOn.net

"guy" <gu*@discussions.microsoft.com> wrote in message
news:E7**********************************@microsof t.com...
why if i do a select on ablock of text (in vs2003) when i do a
find/replace
is find next and replace disabled? replace all is there but i may well not
want to do that?
if i pick any of the other 'search' options replace and find next are
enabled.
why?

guy


Nov 21 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.