Quote:
Originally Posted by DNSB
That is pretty much what I wanted. Not a high priority item as I suspect I may be in a very small group who have multiple searches that are run/not run in sequence.
|
So to expand on this more by thinking out loud (so to speak):
We would store the number of replacements made for every replace all invoked by a "RunSavedSearchReplaceAll" command.
Then we would add 2 new commands:
OnSuccessRunSavedSearchReplaceAll
OnFailedRunSavedSearchReplaceAll
These two commands would conditionally run a saved search replace all depending on the number of replacements stored by the last "RunSavedSearchReplaceAll" command.
If the number of last search replacements was 0, then a OnFailedRunSavedSearchReplaceAll would work to run its search but a OnSuccessRunSavedSearchReplaceAll would not.
If the number of last search replacements was > 0, then a OnFailedRunSavedSearchReplaceAll would *not* run its search but a OnSuccessRunSavedSearchReplaceAll would run its search.
Is this enough logic to do what you want?
Should the two new commands also set the number of last search replacements made if run?
If you could create a small example of how these might be used and why, it would really help me to understand how conditioning on prior search replace all results should be handled.
Thanks,