11th Chapter Application of-delphi Application (i) (1)

Establishment of 11.1 Help file

The Help file is a hypertext assistance file provided by the Micosoft Windows3.0 version. With this hypertext, the Help file system is easily available to users. The Help file is written in the main thread, a topic that jumps to a related topic, or a topic query by keyword. The Help file is combined with software development tools to implement the ' contextual sensitivity ' of the application and to help the system mount automatically. "Context sensitive" refers to the appropriate portion of the Help file that is displayed according to the program's current execution code.

Many of the applications provided by Windows have a Help system in which readers can learn a great deal about the application.

11.1.1 tools and files needed to build Help files

Programmers can create help file systems for their own applications. But to establish the most basic Help system, you must have the following documents

1. WinHelp application (WinHelp.exe). Running the Help system is actually running the Help source file

Windhelp program. The Help file can be run only through the WinHelp file.

2. A word processor that can create a theme. This processor can save files in Rich Text format and create $,#,k,+ feet. The rich-text format format is a file format that can record various textual features. These features include font size, line style, and so on. The Microsoft Word 6.0 processor meets the above requirements.

3. A word processor or editor that can save files in an ASCII format in order to create a Help engineering file (. HPJ file).

4. Help file Compiler (HCP. EXE or HC31.EXE), both compilers compile help files that are used in the Windows3.1 environment, but cannot compile help files in the Windows3.0 environment. HCP. EXE is a protected-mode compiler that can better use memory space. To use the HCP.EXE compiler in Windows DOS window.

5. The error information source file (HCP) required by the Help compiler. ERR or Hc31.err). If an error occurs during compilation of the Help file, the WinHelp runtime prompts for an error message that is stored in the Hcp.err or Hc31.err file.

The following tools enable advanced features of the Help system:

1. Hotspot (Hotspot) editor (shed). EXE);

The Hotspot Editor can create a segmented hyper-image file (. SHG). This file includes several images that are divided into hotspots, and when the user clicks the image, a window pops up or jumps to another topic.

2. Multi-resolution bitmap compiler (MRBE). EXE);

The compiler can combine bitmaps with multiple resolutions into a single file for WinHelp to use. WinHelp Check the resolution of the monitor and display it at the appropriate resolution.

3. Image editor, which can save image files in bitmap form. Use the Image editor to create descriptions and custom buttons.

4. Drawing software. Used to create a metafile (WMF) other than a bitmap;

The programmer can insert the image directly into the text, or you can paste the image into the text with the Windows Clipboard.

Creation of 11.1.2 Help files

The simplest and most straightforward way to create a help file is described below, assuming you create a theme in Word.

The Create Help file is divided into the following 4 steps:

1. Create the theme of the Help file and save it in RTF format;

2. Create Content topics (contents Topic) and save them in RTF format;

3. Create Help engineering documents (. HPJ) to be saved in text format;

4. Compile the project file into a Help source file (. HLP).

11.1.2.1 Create a Theme

A simple Help topic includes topic topics (title), theme text (text), PIN, subject content, global query, print. The topic is best with a topic, the topic is written in the first line of the topic. Use different font sizes and colors to differentiate

When you finish writing the topic, you can enter the text of the topic. Don't worry about the width of each line when you enter. The compiled Help file automatically determines the line width based on the window size. Inserts a page break at the end of the topic, and WinHelp each page as a separate theme.

When writing topic text, be careful to write the text as a small list of paragraphs as much as possible, so that you can easily read and control the length of the topic so that users do not need to use the scroll bar to read the text.

You should include a number of WinHelp in the subject, which identify the theme and provide some guidance control (Novigation controls), as shown in table 11.1 for four typical pin marks.

Table 11.1 foot mark and use

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Symbols apply to use

──────────────────────────────────

# The content string uniquely identifies the subject

$ title Display topic in the Search dialog box and the History list box

K keyword (paragraph) out in the Search dialog box

+ Browse order when users are using

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

The following is a description of the insertion method for four foot marks:

1. Insert # foot mark. Move the cursor to the top end of the theme and insert the # foot sign. The bottom of the topic text also appears #, and then type the content string later. WinHelp uses content strings as the only recognizable topic. Users can never see these strings, but designers use them to define jump topics.

2. Insert $ foot mark, move cursor to # foot mark, insert $ pin. At the bottom of the text, enter the title of the topic, which is the same as the first line, and the title will appear in the Search dialog box and the History dialog.

3. Insert K foot mark. Insert the K-pin after the foot mark in the first line of the topic, and type the fields after the K-pin in the subject text, which appears in the Search list box, as shown in 11.3.