Implementing the FSearch Form

The XEditor control uses a private FSearch form that resides in the control project. Clients of XEditor don’t need to use the form. They might prefer a toolbar, menu, or keyboard interface for search operations. Since the FSearch form is never loaded into memory unless you call the form procedures, it can be ignored without much cost.

For maximum flexibility, all the raw power of finding and replacing is built into XEditor. The FSearch form doesn’t know a thing about how to find or modify text within an editor; it only knows how to handle the buttons and other controls on the form.