| Home | Getting Started | Using the Template | Task Guides | What’s New |
xSearch uses one application-level global extension and one or more browse-specific control templates. The Search control provides searching and tagging for an ABC Browse. Optional companion controls provide Tag/Untag, Tag All, Untag All, Show Tagged, and Export functionality. Add only the controls your browse needs.
On Tag Storage, the Global INI file setting stores search, window and export preferences. A bare filename resolves beside the EXE, or the developer can specify a writable full pathname or a variable prefixed by !. See INI Files and Remembered Settings.
For multi-DLL applications, configure shared definitions in the Data DLL and in the APP containing the browse. See Multi-DLL Setup.
For a tag icon beside an existing column, select that column’s field and enable Transparent icon display in the LIST Formatter, not Normal. Transparent avoids the visible icon bounding box on otherwise untagged rows. The field must already be part of the LIST; see Browse Setup and LIST Icons.
To make tagged records stand out across the whole LIST, open the Search control’s Appearance tab, check Highlight tagged rows, and choose the Background colour. This per-browse option defaults to off and preserves the normal selected-row highlight. See Browse Setup and LIST Icons.
For editable dialog windows, import a complete Classic or Modern set using Application > Template Utility (or import individual windows), then select procedures on the global Windows tab. The original class windows remain the default. See Customize xSearch Windows.
Once Search has been placed, companion xSearch control templates become available. Add the buttons needed by the browse. See Search and Tag Controls.
After searching and tagging, add xSearch 5.0 for Report to an appropriate Clarion report procedure, or xSearch 5.0 for Process to a process procedure. Match the tag-store method and unique record field to the tagging browse. You can then call the report or process through its usual menu or button; the xSearch procedure extension can ask whether to work with the tagged subset. The call button itself does not require special xSearch code. See Reports and Processes Using Tags.
Fomin Report Builder: On a supported Fomin RunTimeReport procedure, use xSearch 5.0 for Fomin Report Builder to make its report operate on tagged records. The ordinary report and process extensions are for their respective Clarion procedure types. The two other procedure extensions, alternate window and alternate export window, are already included when you import xSearch’s editable Classic or Modern windows. See All Five Procedure Extensions.
In the application tree, right-click the browse procedure and choose Extensions. Double-click Search this browse and tag what it finds to reopen its template settings without returning to Window Designer.
For step-by-step examples, see Single-EXE Setup or Multi-DLL Setup.
| Home | Getting Started | Using the Template | Task Guides | What’s New |