#Code/Replace is a Pain!
5 messages in this thread
Hi Jack,
You know I have never heard anyone else having that problem. I never
read my options and always "double click" on the file and the dialog goes
away and I am stuck with having to go back to an older version. I was
thinking about it last night and thought that it wasn't the best choice.
You must have been reading my mind. I will add it the "wish" list for
future releases.
Don Funk
There is 1 Reply.
Don:
In my case 'replace' is exactly the default option I prefer; I rarely
'merge' any text. If you're going to change the default I hope you make
what the default is an option.
While I have your ear, I would also like an easy way to 'save'/'replace'
the text from a number of files at once. I often save the text-files to do
off-line editing and having to save/replace file by file is inconvenient.
LEE
There is 1 Reply.
Hi Lee,
Yes I too agree that the merge should be the default. I have added this
as a suggestion for future release.
Also there is no way in VB to save *all* files as a text file(s) at
once. This has already been suggested for future releases.
Thanks, Don Funk
There are 2 Replies.
Don,
NO! Please don't change the the default to MERGE! It's enough work now to
save/replace modules now in order to clean them up, and making Merge the
default would only make it more drudgery. How about a simple macro of some
kind to save/replace all modules prior to a compile? That would be
fantastic.
–dennis
Don:
I think you mis-read my response — I want 'replace' to be the default. If
there are plans to change the default to 'merge' then IMO the default
should be configurable.
I'm glad to hear that save/replace of multiple files at once is on the
suggestion list for the future. Any idea if it's being planned for the
next release, or will the wait be longer?
LEE