home *** CD-ROM | disk | FTP | other *** search
Text File | 1995-02-15 | 48.1 KB | 1,477 lines |
- .rem(=================================)
- .rem(| Macro File for HelpGen Help |)
- .rem(|Copyright 1994 Rimrock Software|)
- .rem(| All rights reserved. |)
- .rem(=================================)
- .start(main,Contents,HLPGEN.BMP,HelpGen Help)
- .top(Help)
- .top(Table of Contents)
- .n
- .b(Purpose) - Click on icon above.n.n
- .b(How to).n
- .in
- ##.j(lodmac,Load or Create a Macro file)
- ##.j(crehpj,Load or Create a Project File)
- ##.j(bldrtf,Build an RTF File)
- ##.j(bldhlp,Build a Help File)
- ##.j(lang,Use the HelpGen Macro Language)
- .un
- .n
- .b(Menu Commands).n
- .in
- ##.j(file,File Commands)
- ##.j(edit,Edit Commands)
- ##.j(generate,Build Commands)
- ##.j(testem,Test Command)
- ##.j(options,Option Commands)
- ##.j(help,Help Commands)
- .un
- .n
- .bj(glossary,demo.bmp)
- \tab
- .b(Glossary).n
- .n
- If you are unfamiliar with how Windows Help works, choose
- .b(Help | How To Use Help) from the Help menu now.
- .end
- .rem(=================================)
- .rem( Icon topic )
- .rem(=================================)
- .ent(icon,Information,HelpGen ) \qc
- HelpGen version 1.21. \'a9 1994 by Rimrock Software, all rights reserved..n.n \ql
- Under normal circumstances, if you want to create a help file with
- the Windows help compiler, you must first create a help topic file
- using a word processor that can save files in Rich Text Format (.p1(RTF)).
- There are several basic problems with that approach:.n
- .in
- #n(1)Word processors cost a lot of money..n
- #n(2)Once you've purchased the word processor, you have to
- learn how to use it. This may not be a very productive use of
- your programming time..n
- #n(3)You also have to learn how to use the word processor to
- produce a file that is properly formatted for the help compiler.
- This involves using items like underlining, double-underlining,
- hidden text, footnotes, etc..n
- .un
- HelpGen eliminates these problems by allowing you to use your
- favorite ASCII text editor to produce a HelpGen .p1(macro) file, which
- HelpGen uses to create the RTF formatted file required by the
- help compiler..n.n
- HelpGen automates the entire process of creating help files:.n
- .in
- ##Creates a skeleton macro file for you to edit.
- ##Invokes your editor to allow you to edit the macro file.
- ##Creates a help project file (.HPJ) to tell the help
- compiler how to compile the help file.
- ##Generates an RTF file from the macro file.
- ##Invokes the help compiler to compile the RTF file into a
- HLP file.
- ##Allows you to directly test the result..n
- .n
- .box
- The HelpGen macro engine is based on code written by David Spector, and published
- in Windows/DOS Developer's Journal, Vol. 5, No. 7, July 1994.
- .bend
- .end
- .rem(=================================)
- .rem( Load/Create macros topic )
- .rem(=================================)
- .ent(lodmac,Load/Create Macro File,How to )
- Select the .b(File | Open Macro File) menu option. Select an existing .MAC file
- or enter the name of a new file. If you enter the name of a file that does not
- exist, HelpGen will create the file for you, using a .p1(template) that contains the
- minimum items required to build a help file..n
- .n
- If you have created a new .p1(macro) file, you should use the .b(Edit | Macro File)
- option to make two changes to the file. The first change is a new title for
- the table of contents. The default title is xxxx. The second change is the
- selection of a .BMP graphic to place on the table of contents title line. The
- default is HlpGen.BMP.
- .end
- .rem(=================================)
- .rem( Load/Create project file topic )
- .rem(=================================)
- .ent(crehpj,Load/Create Project File,How to )
- HelpGen looks for an associated .p1(project) file when you open the current macro
- file. If it finds one, HelpGen will enable the .b(Edit | Project File) menu
- item, and you won't have to build a project file. If it doesn't find a project
- file, HelpGen will enable the .b(Build | Project File) menu item to allow you to
- create a project file. You must select .b(Build | Project File) to
- create the new project file..n
- .n
- .box
- .b(NOTE:) Before you build a project file, select the .b(Options | Project File)
- menu item and make sure that all the items in that dialog are to your liking.
- Those items will be used to create the project file.
- .bend
- .end
- .rem(=================================)
- .rem( how to build RTF file topic )
- .rem(=================================)
- .ent(bldrtf,Build an RTF File,How to )
- Select the .b(Build | RTF File) menu item. HelpGen will ask you if you are sure
- you want to create an .p1(RTF) file. If you answer 'yes', HelpGen will create a .RTF
- file by processing the .MAC file. Macros will be expanded and .p(rtfcmds,RTF commands) and
- plain text will be passed through to the .RTF file. When processing is complete,
- HelpGen will tell you and will then enable the .b(Build | HLP File) menu item.
- .end
- .rem(=================================)
- .rem( how to build help file topic )
- .rem(=================================)
- .ent(bldhlp,Build a Help File,How to )
- Select the .b(Build | HLP File) menu item. HelpGen will ask you if you are sure
- you want to create a help file. If you answer 'yes', HelpGen will invoke the
- .p(hlpcmplr,help compiler) you have selected in the .b(Options | Directories) menu item. This
- will involve shelling out to DOS, since help compilers are DOS programs. When
- HelpGen gets control again, it will enable the .b(Test) menu item, to allow you
- to test the help file you have just created..n
- .n
- If there were errors generated during the help compilation, they will be listed in
- the error log file that is shown in .b(Options | Project File)..n
- .n
- .box
- .b(NOTE:) When HelpGen invokes the help compiler, and for some reason the compiler
- can't execute, HelpGen will notify you by displaying an error message. To possibly
- correct your problem, make sure that the proper help compiler is correctly chosen in
- HelpGen's .b(Options | Directories) menu item.
- .bend
- .end
- .rem(=================================)
- .rem( using helpgen TOC topic )
- .rem(=================================)
- .ent(lang,Macro Language,Using the HelpGen )
- .in
- ##.j(langbas,Macro Language Basics)
- ##.j(maccmd,Macro Language Commands)
- ##.j(rtfcmd,Useful RTF Commands)
- .un
- .end
- .rem(=================================)
- .rem( file commands topic )
- .rem(=================================)
- .ent(file,File Commands,The )
- .in
- ##.j(open,Open Macro File)
- ##.j(close,Close Macro File)
- ##.j(print,Print Macro File)
- ##.j(exit,Exit)
- .un
- .end
- .rem(=================================)
- .rem( edit commands TOC topic )
- .rem(=================================)
- .ent(edit,Edit Commands,The )
- .in
- ##.j(editmac,Edit Macro File)
- ##.j(edithpj,Edit Project File)
- .un
- .end
- .rem(=================================)
- .rem( build commands TOC topic )
- .rem(=================================)
- .ent(generate,Build Commands,The )
- .in
- ##.j(genhpj,Project File)
- ##.j(genrtf,RTF File)
- ##.j(genhlp,HLP File)
- .un
- .end
- .rem(=================================)
- .rem( test command topic )
- .rem(=================================)
- .ent(testem,Test Command,The )
- The .b(Test) menu item allows you to test the help file that you have
- just generated. It will only be enabled after you have generated a
- help file.
- .s
- .bmpl(testrtf.bmp)You may also select this menu item with the .p1(toolbar)
- Test Help File button.
- .end
- .rem(=================================)
- .rem( options commands TOC topic )
- .rem(=================================)
- .ent(options,Options Commands,The )
- .in
- ##.j(optdir,Directories)
- ##.j(opthpj,Project File)
- .un
- .end
- .rem(=================================)
- .rem( help commands TOC topic )
- .rem(=================================)
- .ent(help,Help Commands,The )
- .in
- ##.j(hlpcon,Contents)
- ##.j(about,About HelpGen)
- .un
- .end
- .rem(=================================)
- .rem( open macro file topic )
- .rem(=================================)
- .ent(open,Open Macro File, )
- Open an existing .p1(macro) file, or create a new macro file to be edited
- (.b(File | Open Macro File) menu item). A check will be made for a
- corresponding .p1(project) file. If a project file exists, then the
- .b(Edit | Project File) menu item will be enabled. If a project file does
- not exist, then the .b(Build | Project File) menu item will be enabled.
- The HelpGen .p(titlebar,title bar) is updated to reflect the current macro file name.
- .s
- .bmpl(openrtf.bmp)You may also select this menu item with the .p1(toolbar) Open
- Macro File button.
- .end
- .rem(=================================)
- .rem( close macro file topic )
- .rem(=================================)
- .ent(close,Close Macro File, )
- The Close command closes all files and disables all HelpGen menu items that are
- associated with open files (.b(File | Close Macro File) menu item). The
- HelpGen .p(titlebar,title bar) is updated to show that no .p1(macro) file is currently open.
- .s
- .bmpl(closertf.bmp)You may also select this menu item with the .p1(toolbar) Close
- Macro File button.
- .end
- .rem(=================================)
- .rem( print macro file topic )
- .rem(=================================)
- .ent(print,Print Macro File, )
- The Print command will print the current .p1(macro) file on any printer
- (.b(File | Print Macro File) menu item). You will be asked to select the
- proper printer before any printing takes place.
- .s
- .bmpl(printrtf.bmp)You may also select this menu item with the .p1(toolbar) Print
- Macro File button.
- .end
- .rem(=================================)
- .rem( exit topic )
- .rem(=================================)
- .ent(exit,Exit to Program Manager, )
- The Exit command closes all open files and shuts down the HelpGen program
- (.b(File | Exit) menu item).
- .end
- .rem(=================================)
- .rem( edit macro file topic )
- .rem(=================================)
- .ent(editmac,Edit Macro File, )
- The .b(Edit | Macro File) command executes a text editor and allows you to make
- changes to the current .p1(macro) file. The default text editor is NOTEPAD.EXE. The
- default editor may be changed using the .b(Options | Directories) menu item.
- .s
- .bmpl(edmacrtf.bmp)You may also select this menu item with the .p1(toolbar) Edit
- Macro File button.
- .s
- .box
- .b(NOTE:) When HelpGen invokes the text editor, and for some reason the editor
- can't be executed, HelpGen will notify you by displaying an error message.
- To possibly correct your problem, make sure that the text editor is correctly
- chosen in HelpGen's Options | Directories menu item.
- .bend
- .end
- .rem(=================================)
- .rem( edit project file topic )
- .rem(=================================)
- .ent(edithpj,Edit Project File, )
- The .b(Edit | Project File) menu item executes a text editor and allows you to make
- changes to the current .p1(project) file. The default text editor is NOTEPAD.EXE. The
- default editor may be changed using the .b(Options | Directories) menu item.
- .s
- .bmpl(edhpjrtf.bmp)You may also select this menu item with the .p1(toolbar) Edit
- Project File button.
- .s
- .box
- .b(NOTE:) When HelpGen invokes the text editor, and for some reason the editor
- can't execute, HelpGen will notify you by displaying an error message.
- To possibly correct your problem, make sure that the text editor is correctly
- chosen in HelpGen's Options | Directories menu item.
- .bend
- .end
- .rem(=================================)
- .rem( build project file topic )
- .rem(=================================)
- .ent(genhpj,Build Project File, )
- If you don't yet have a .p1(project) file for your current .p1(macro) file, this menu
- item will be enabled (.b(Build | Project File) menu item). It will create
- a project file for you, based on the entries contained in the .b(Options) menu.
- You may then make any changes to this file using the .b(Edit | Project File)
- menu item. The project file will have the same filename as the macro file,
- with an extension of .HPJ.
- .s
- .bmpl(buhpjrtf.bmp)You may also select this menu item with the .p1(toolbar) Build
- Project File button.
- .end
- .rem(=================================)
- .rem( build RTF file topic )
- .rem(=================================)
- .ent(genrtf,Build RTF File, )
- The .b(Build | RTF File) menu item uses the current .p1(macro) file to build a Rich Text
- Format (.p1(RTF)) file of the same name. The RTF file is used as an input file for
- the .p(hlpcmplr,help compiler).
- .s
- .bmpl(burtfrtf.bmp)You may also select this menu item with the .p1(toolbar) Build
- RTF File button.
- .end
- .rem(=================================)
- .rem( build HLP file topic )
- .rem(=================================)
- .ent(genhlp,Build HLP File, )
- The .b(Build | HLP File) menu item uses the current .p1(project) file and the .p1(RTF) file
- created by HelpGen to create a Microsoft Help File (HLP). It does this by
- invoking the Microsoft (or other) help compiler. The default help compiler is
- HC31.EXE. You may change the default help compiler by using the .b(Options | Directories)
- menu item.
- .s
- .bmpl(buhlprtf.bmp)You may also select this menu item with the .p1(toolbar) Build
- HLP File button.
- .s
- .box
- .b(NOTE:) When HelpGen invokes the help compiler, and for some reason the compiler
- can't execute, HelpGen will notify you by displaying an error message. To possibly
- correct your problem, make sure that the proper help compiler is correctly chosen in
- HelpGen's Options | Directories menu item.
- .bend
- .end
- .rem(=================================)
- .rem( directories options topic )
- .rem(=================================)
- .ent(optdir,Directories,Set )
- The .b(Options | Directories) menu item allows you to select the .p(hlpcmplr,help compiler)
- and text editor that HelpGen uses when building a help file or editing text. The
- entries that you make are also saved in HelpGen's .INI file and will be used each
- time you execute HelpGen.
- .end
- .rem(=================================)
- .rem( project file options topic )
- .rem(=================================)
- .ent(opthpj,Project File Options,Set )
- The .b(Options | Project File) menu item allows you to specify the options that
- will be installed in a .p1(project) file that is created by HelpGen. Some of these
- options are saved in HelpGen's .INI file, so they may be used in subsequent
- executions of HelpGen. Specifically, the Compression type, Warnings, Report status,
- Copyright notice and Error Log are all saved in the .INI file..n
- .n
- .i(Title).n
- The Title specifies the string that is placed on the Help File's .p(titlebar,title bar) when the help
- file is executed..n
- .n
- .i(Copyright).n
- The Copyright specifies the string that is placed inside of the help file's About box.
- This box is activated by executing the help file and selecting .b(Help | About Help)..n
- .n
- .i(Error Log).n
- The Error Log is the file that the .p(hlpcmplr,help compiler) uses to write error messages to. If
- you have errors during a help compilation, look at this file to see what the errors
- were..n
- .n
- .i(Icon File).n
- The Icon File entry specifies the icon that will be used when the help file is minimized.
- This entry will override the default question mark icon..n
- .n
- .i(Bitmap Root).n
- The Bitmap Root specifies the directory that is used to store bitmap files, if they
- are not in the current directory..n
- .n
- .i(Compression).n
- The Compression option specifies what type of compression is used when building
- the help file. .b(0) specifies no compression, .b(Medium) specifies 40% compression
- and .b(High) specifies 50% compression..n
- .n
- .i(Warnings).n
- The Warnings option sets the level of error messages that the help
- compiler will display during compilation. .b(Some) means only the most severe messages will
- be displayed, .b(Many) means a medium amount of error messages will be displayed,
- and .(All) means display all messages..n
- .n
- .i(Report).n
- The Report option determines the type of error messages that are displayed
- during help file compilation.
- .end
- .rem(=================================)
- .rem( help contents topic )
- .rem(=================================)
- .ent(hlpcon,Help Contents, )
- The .b(Help | Contents) menu item executes the help file you are currently reading.
- .s
- .bmpl(helprtf.bmp)You may also select this menu item with the .p1(toolbar) Help
- Contents button.
- .end
- .rem(=================================)
- .rem( about helpgen topic )
- .rem(=================================)
- .ent(about,About HelpGen, )
- The .b(Help | About HelpGen) menu item provides information about the current version
- of the HelpGen program.
- .end
- .rem(=================================)
- .rem( language basics topic )
- .rem(=================================)
- .ent(langbas,Language Basics, )
- HelpGen Macro Files consist of distinct blocks of text. These blocks are
- marked by HelpGen .p(macro,macros). The first block is the \'2estart/\'2eend/\'2eend_file block:.n
- .n
- .[
- \li720
- \'2estart(......).n
- \tab Table of Contents stuff here.....n
- \'2eend.n.n
- \tab Rest of macro file goes here.....n.n
- \'2eend_file.n
- .]
- .n
- The rest of the macro file is broken up into \'2eent/\'2eend and
- \'2epent/\'2eend blocks:.n
- .n
- .[
- \li720
- \'2estart(......).n
- \tab Table of Contents stuff here.....n
- \'2eend.n.n
- \'2eent(.....).n
- \tab Topic stuff here.....n
- \'2eend.n.n
- \'2eent(.....).n
- \tab Topic stuff here.....n
- \'2eend.n.n
- \'2eent(.....).n
- \tab Topic stuff here.....n
- \'2eend.n.n
- \'2epent(.....).n
- \tab Popup stuff here.....n
- \'2eend.n.n
- \'2epent(.....).n
- \tab Popup stuff here.....n
- \'2eend.n.n
- \'2eend_file.n
- .]
- .n
- Note the use of white space to separate the various blocks. You may
- also separate the blocks with remarks:.n
- .n
- .[
- \li720
- \'2erem(===== Beginning of topic 1 =====).n
- \'2eent(.....).n
- \tab Topic stuff here.....n
- \'2eend.n
- \'2erem(===== Beginning of topic 2 =====).n
- \'2eent(.....).n
- \tab Topic stuff here.....n
- \'2eend.n
- .]
- .n
- In order to display each of these blocks, you need to have jumps (\'2ej or
- \'2ej1 for the \'2eent/\'2eend blocks and \'2ep or \'2ep1 for the
- \'2epent/\'2eend blocks) somewhere in your macro file. Since the help
- file begins at the Table of Contents, there should definitely be some
- jumps in that .p1(topic)..n
- .n
- All the rest of the HelpGen macros are basically window dressing for
- the topic blocks. See the various macro commands for examples of how
- to use them..n
- .n
- HelpGen generates an RTF file that specifies four basic text fonts;
- font 0 is MS San Serif, font 1 is Roman, font 2 is Courier and font 3
- is Symbol. Font 0 is used for topic headers, font 1 is used for
- normal text in a topic and font 2 is used inside of the \'2e[ and
- \'2e] macros. Font 3 is not currently used..n
- .end
- .rem(=================================)
- .rem( macro commands TOC topic )
- .rem(=================================)
- .ent(maccmd,Macro Language Commands, )
- .in
- ##.j(cmdstr,\'2estart)
- ##.j(cmdent,\'2eent)
- ##.j(cmdpent,\'2epent)
- ##.j(cmdend,\'2eend)
- ##.j(cmdj,\'2ej)
- ##.j(cmdj1,\'2ej1)
- ##.j(cmdp,\'2ep)
- ##.j(cmdp1,\'2ep1)
- ##.j(cmdbj,\'2ebj)
- ##.j(cmdtop,\'2etop)
- ##.j(cmdbmp,\'2ebmp)
- ##.j(cmdbmpl,\'2ebmpl)
- ##.j(cmdbmpr,\'2ebmpr)
- ##.j(cmdbox,\'2ebox)
- ##.j(cmdbend,\'2ebend)
- ##.j(cmdrem,\'2erem)
- ##.j(cmdin,\'2ein)
- ##.j(cmdun,\'2eun)
- ##.j(cmdpp,\'23\'23)
- ##.j(cmdpb,\'23b)
- ##.j(cmdpn,\'23n)
- ##.j(cmdb,\'2eb)
- ##.j(cmdi,\'2ei)
- ##.j(cmdob,\'2e[)
- ##.j(cmdcb,\'2e])
- ##.j(cmdn,\'2en)
- ##.j(cmds,\'2es)
- ##.j(cmdef,\'2eend_file)
- .un
- .end
- .rem(=================================)
- .rem( RTF commands TOC topic )
- .rem(=================================)
- .ent(rtfcmd,RTF Commands,Some Useful )
- .in
- ##.j(cmdbrdrdb,\\brdrdb)
- ##.j(cmdbrdrs,\\brdrs)
- ##.j(cmdbrdrsh,\\brdrsh)
- ##.j(cmdbrdrth,\\brdrth)
- ##.j(cmdli,\\li)
- ##.j(cmdri,\\ri)
- ##.j(cmdql,\\ql)
- ##.j(cmdqr,\\qr)
- ##.j(cmdqj,\\qj)
- ##.j(cmdqc,\\qc)
- ##.j(cmdtab,\\tab)
- ##.j(cmdhh,\\'hh)
- .un
- .n
- .box
- .b(NOTE:) All .p(rtfcmds,RTF commands) should be separated from regular
- text by some kind of 'white space'. This includes a space (' ') or a
- carriage return.
- .bend
- .end
- .rem(=================================)
- .rem( start macro topic )
- .rem(=================================)
- .ent(cmdstr,\'2estart Macro,The )
- .b(SYNTAX:) \'2estart(label,topic,bitmap_file,application_name).n
- .n
- .b(EXPLANATION:) This .p1(macro) marks the beginning of a macro file.
- It produces an attractive header for the Table of Contents .p1(topic).
- .b(label) and .b(topic) are as described for the \'2eent macro.
- .b(bitmap_file) is the filename of a \'2eBMP file generated by
- a bitmap editor such as Windows Paintbrush. .b(application_name)
- is the title that will appear in the header of the Table of
- Contents topic. You must provide a topic entry labeled 'icon'
- which will be jumped to when the user clicks on the icon in the
- Table of Contents header. The \'2estart statement also requires
- a corresponding \'2eend to indicate the end of the table of contents..n
- .n
- .b(EXAMPLE:).n.n
- .[
- \li720
- \'2estart(main,Contents,DEMO\'2eBMP,A Help Demonstration).n
- This is the table of contents topic. It is ended by the
- next line..n
- \'2eend.n
- .n
- \'2eent(icon,Version,Help File ).n
- This is a mandatory topic. We jump to here when the
- DEMO\'2eBMP icon is clicked..n
- \'2eend.n
- .n
- \'2eend_file.n
- .]
- .n
- .b(SEE ALSO:) .j(cmdef,\'2eend_file)
- .end
- .rem(=================================)
- .rem( ent macro topic )
- .rem(=================================)
- .ent(cmdent,\'2eent Macro,The )
- .b(SYNTAX:) \'2eent(label,topic,prefix).n
- .n
- .b(EXPLANATION:) This .p1(macro) marks the start of a .p1(topic) entry.
- .b(label) is used to refer to the topic in the \'2ej and \'2ej1
- macros, .b(topic) is the name that will appear in
- the topic header and in the Search dialog box; and .b(prefix) is a
- string that will appear as a prefix in the header (if the topic is
- "Frogs" and the prefix is "The", the header will be "The Frogs" but
- the entry in the Search dialog box will be "Frogs"). The prefix can
- be an empty string..n
- .n
- .b(EXAMPLE:).n
- .n
- .[
- \li720
- \'2eent(file,File Commands, ).n
- \'2ein.n
- \'23\'23\'2ej(open,Open File)\'2en.n
- \'2eun.n
- \'2eend.n
- .n
- \'2eent(open,Open File, ).n
- This command allows you to open an existing file..n
- \'2eend.n.n
- .]
- .b(SEE ALSO:) .j(cmdend,\'2eend), .j(cmdj,\'2ej), .j(cmdj1,\'2ej1).n
- .end
- .rem(=================================)
- .rem( pent macro topic )
- .rem(=================================)
- .ent(cmdpent,\'2epent Macro,The )
- .b(SYNTAX:) \'2epent(label,topic).n
- .n
- .b(EXPLANATION:) This .p1(macro) is identical to \'2eent, except
- that it creates .p1(popup) topic boxes instead of .p1(topic) pages.
- This type of popup box is usually used for definitions. .b(label)
- is used to refer to the topic in the \'2ep and \'2ep1 macros
- described below. .b(topic) should match the topic label in
- the corresponding \'2ep or \'2ep1 macro..n
- .n
- .b(EXAMPLE:).n
- .n
- .[
- \li720
- \'2eent(size,Font Size,Changing ).n
- This item allows you to change the size of the display font. The
- new size can be anywhere from 6 \'2ep1(points) to 72 points..n
- \'2eend.n
- .n
- \'2epent(points,Points).n
- A sizing standard for text. There are 72 points to the inch.
- Therefore, 6 points is 6/72" = 1/12"..n
- \'2eend.n.n
- .]
- .b(SEE ALSO:) .j(cmdend,\'2eend), .j(cmdp,\'2ep), .j(cmdp1,\'2ep1).n
- .end
- .rem(=================================)
- .rem( end macro topic )
- .rem(=================================)
- .ent(cmdend,\'2eend Macro,The )
- .b(SYNTAX:) \'2eend.n
- .n
- .b(EXPLANATION:) This .p1(macro) marks the end of a .p1(topic) entry
- that was started with \'2eent or \'2epent..n
- .n
- .b(EXAMPLE:) See the examples for \'2estart, \'2eent and \'2epent..n
- .n
- .b(SEE ALSO:) .j(cmdstr,\'2estart), .j(cmdent,\'2eent), .j(cmdpent,\'2epent).n
- .end
- .rem(=================================)
- .rem( j macro topic )
- .rem(=================================)
- .ent(cmdj,\'2ej Macro,The )
- .b(SYNTAX:) \'2ej(label,string).n
- .n
- .b(EXPLANATION:) This .p1(macro) creates an underlined .b(string) and
- uses the string as a jump area. If the user clicks on a jump area,
- the .p1(topic) represented by .b(label) is shown on the screen..n
- .n
- .b(EXAMPLE:).n
- .n
- .[
- \li720
- \'2eent(layout,Page Layout,The ).n
- How to Lay Out.n
- \'2es.n
- \'2ej(pageno,Page Numbers)\'2en.n
- \'2ej1(Headers)\'2en.n
- \'2ej1(Footers)\'2en.n
- \'2eend.n
- .n
- \'2eent(pageno,Page Numbers, Laying Out ).n
- Text for page number layout goes here..n
- \'2eend.n
- .n
- \'2eent(Headers,Headers,Laying Out ).n
- Text for page header layout goes here..n
- \'2eend.n
- .n
- \'2eent(Footers,Footers,Laying Out ).n
- Text for page footer layout goes here..n
- \'2eend.n.n
- .]
- .b(SEE ALSO:) .j(cmdent,\'2eent), .j(cmdj1,\'2ej1), .j(cmdbj,\'2ebj).n
- .end
- .rem(=================================)
- .rem( j1 macro topic )
- .rem(=================================)
- .ent(cmdj1,\'2ej1 Macro,The )
- .b(SYNTAX:) \'2ej1(label).n
- .n
- .b(EXPLANATION:) This .p1(macro) is identical to a \'2ej with its
- .b(label) and .b(string) being identical. This macro is used for
- brevity..n
- .n
- .b(EXAMPLE:) See the example for the \'2ej command..n
- .n
- .b(SEE ALSO:) .j(cmdent,\'2eent), .j(cmdj,\'2ej).n
- .end
- .rem(=================================)
- .rem( p macro topic )
- .rem(=================================)
- .ent(cmdp,\'2ep Macro,The )
- .b(SYNTAX:) \'2ep(label,string).n
- .n
- .b(EXPLANATION:) This .p1(macro) underlines .b(string) with a dotted
- line and uses it as a jump area. If the user clicks on the jump area,
- the topic represented by .b(label) is shown in a .p1(popup) window.
- This is used to show definitions..n
- .n
- .b(EXAMPLE:).n
- .n
- .[
- \li720
- \'2eent(cmds,Keyboard Commands,New ).n
- The keyboard that supports Chicago has three extra keys; the
- \'2ep1(LWIN) key, the \'2ep1(RWIN) key and the \'2ep(application,APP) key..n
- \'2eend.n
- .n
- \'2epent(application,APP).n
- When pressed, brings up the context menu at the current select
- position..n
- \'2eend.n
- .n
- \'2epent(LWIN,LWIN).n
- Sets the focus to the Chicago User Interface. Same
- functionality as the RWIN key, but uses a different
- scan code..n
- \'2eend.n
- .n
- \'2epent(RWIN,RWIN).n
- Sets the focus to the Chicago User Interface. Same
- functionality as the LWIN key, but uses a different
- scan code..n
- \'2eend.n.n
- .]
- .b(SEE ALSO:) .j(cmdpent,\'2epent), .j(cmdp1,\'2ep1).n
- .end
- .rem(=================================)
- .rem( p1 macro topic )
- .rem(=================================)
- .ent(cmdp1,\'2ep1 Macro,The )
- .b(SYNTAX:) \'2ep1(label).n
- .n
- .b(EXPLANATION:) This .p1(macro) is identical to \'2ep with its
- .b(label) and .b(string) being identical. This macro can be used
- for brevity..n
- .n
- .b(EXAMPLE:) See the example for the \'2ep command..n
- .n
- .b(SEE ALSO:) .j(cmdpent,\'2epent), .j(cmdp,\'2ep).n
- .end
- .rem(=================================)
- .rem( bj macro topic )
- .rem(=================================)
- .ent(cmdbj,\'2ebj Macro,The )
- .b(SYNTAX:) \'2ebj(label,bitmap_name).n
- .n
- .b(EXPLANATION:) This .p1(macro) is creates a graphical jump area
- using .b(bitmap_name) as the graphic. If the user clicks on the
- jump area, the topic represented by .b(label) is shown on the screen..n
- .n
- .b(EXAMPLE:).n
- .n
- .[
- \li720
- \'2eent(filecmds,File Commands, ).n
- \'2ebj(new,new\'2ebmp) New File.n
- \'2ebj(open,open\'2ebmp) Open File.n
- \'2ebj(close,close\'2ebmp) Close File.n
- \'2eend.n
- .n
- \'2eent(new,New File, ).n
- Text for new file command goes here..n
- \'2eend.n
- .n
- \'2eent(open,Open File, ).n
- Text for open file command goes here..n
- \'2eend.n
- .n
- \'2eent(close,Close File, ).n
- Text for close file command goes here..n
- \'2eend.n
- .n
- .]
- .b(SEE ALSO:) .j(cmdent,\'2eent), .j(cmdj,\'2ej).n
- .end
- .rem(=================================)
- .rem( top macro topic )
- .rem(=================================)
- .ent(cmdtop,\'2etop Macro,The )
- .b(SYNTAX:) \'2etop(string).n
- .n
- .b(EXPLANATION:) This .p1(macro) is used inside of \'2eent and \'2epent
- entries to add .b(string) as another associated topic name to the
- Search dialog box..n
- .n
- .b(EXAMPLE:).n
- .n
- .[
- \li720
- \'2epent(mouse,Pointing Devices).n
- \'2etop(Trackball).n
- \'2etop(Graphics Tablet).n
- \'2etop(Mouse).n
- \'2etop(Pointing Stick).n
- \'2etop(Joy Stick).n
- A device that moves the graphical cursor around the
- screen and that allows you to select objects..n
- \'2eend.n.n
- .]
- .b(SEE ALSO:) .j(cmdent,\'2eent), .j(cmdpent,\'2epent).n
- .end
- .rem(=================================)
- .rem( bmp macro topic )
- .rem(=================================)
- .ent(cmdbmp,\'2ebmp Macro,The )
- .b(SYNTAX:) \'2ebmp(pathname).n
- .n
- .b(EXPLANATION:) This .p1(macro) inserts a named \'2eBMP bitmap
- file on the current line. The bitmap is positioned as though it
- were just another character..n
- .n
- .b(EXAMPLE:).n
- .n
- .[
- \li720
- \'2eent(open,Open Macro File, ).n
- Use the \'2ebmp(openrtf\'2ebmp) Open Macro File button to open the file..n
- \'2eend.n.n
- .]
- .b(SEE ALSO:) .j(cmdbmpl,\'2ebmpl), .j(cmdbmpr,\'2ebmpr).n
- .end
- .rem(=================================)
- .rem( bmpl macro topic )
- .rem(=================================)
- .ent(cmdbmpl,\'2ebmpl Macro,The )
- .b(SYNTAX:) \'2ebmpl(pathname).n
- .n
- .b(EXPLANATION:) This .p1(macro) inserts a named \'2eBMP bitmap
- file at the far left side of the current line. Any text following
- the \'2ebmpl entry is wrapped around the bitmap..n
- .n
- .b(EXAMPLE:).n
- .n
- .[
- \li720
- \'2eent(close,Close Macro File, ).n
- \'2ebmpl(closertf\'2ebmp)Close the macro file and all associated
- files. Disable any menu items relating to open files..n
- \'2eend.n.n
- .]
- .b(SEE ALSO:) .j(cmdbmp,\'2ebmp), .j(cmdbmpr,\'2ebmpr).n
- .end
- .rem(=================================)
- .rem( bmpr macro topic )
- .rem(=================================)
- .ent(cmdbmpr,\'2ebmpr Macro,The )
- .b(SYNTAX:) \'2ebmpr(pathname).n
- .n
- .b(EXPLANATION:) This .p1(macro) inserts a named \'2eBMP bitmap
- file at the far right side of the current line. Any text following
- the \'2ebmpr entry is wrapped around the bitmap..n
- .n
- .b(EXAMPLE:).n
- .n
- .[
- \li720
- \'2eent(keydisp,Key Information,Display ).n
- \'2ebmpr(keydisp\'2ebmp)The key display area shows
- the scan codes that will be sent for this particular
- key - unshifted, shifted, control and alternate..n
- \'2eend.n.n
- .]
- .b(SEE ALSO:) .j(cmdbmp,\'2ebmp), .j(cmdbmpl,\'2ebmpl).n
- .end
- .rem(=================================)
- .rem( box macro topic )
- .rem(=================================)
- .ent(cmdbox,\'2ebox Macro,The )
- .b(SYNTAX:) \'2ebox.n
- .n
- .b(EXPLANATION:) This .p1(macro) draws a box around the current
- paragraph. It applies to all subsequent paragraphs up to the
- \'2ebend command. Box drawing should only be done in normal
- text areas in \'2eent or \'2epent areas..n
- .n
- .b(EXAMPLE:).n
- .n
- .[
- \li720
- \'2eent(about,About HelpGen, ).n
- Display a box containing version information and
- copyright information..n
- \'2en.n
- \'2ebox.n
- \'2eb(NOTE:) The integer portion of the version number
- indicates a major revision and the decimal portion
- indicates a minor revision..n
- \'2ebend.n
- \'2es.n
- All dialog boxes use icon-style pushbuttons and
- graphical elements..n
- \'2eend.n.n
- .]
- .b(SEE ALSO:) .j(cmdbend,\'2ebend).n
- .end
- .rem(=================================)
- .rem( bend macro topic )
- .rem(=================================)
- .ent(cmdbend,\'2ebend Macro,The )
- .b(SYNTAX:) \'2ebend.n
- .n
- .b(EXPLANATION:) This .p1(macro) completes the box drawing that was
- started with a \'2ebox command..n
- .n
- .b(EXAMPLE:) See the \'2ebox example..n
- .n
- .b(SEE ALSO:) .j(cmdbox,\'2ebox).n
- .end
- .rem(=================================)
- .rem( rem macro topic )
- .rem(=================================)
- .ent(cmdrem,\'2erem Macro,The )
- .b(SYNTAX:) \'2erem(text).n
- .n
- .b(EXPLANATION:) This .p1(macro) allows comments to be inserted
- into the macro file..n
- .n
- .b(EXAMPLE:).n
- .n
- .[
- \li720
- \'2erem(-----------------------------------------------).n
- \'2erem( Macro file for RENAULT.EXE help).n
- \'2erem(-----------------------------------------------).n
- \'2estart(main,Contents,renault\'2ebmp,Renault Help).n
- \'2erem(Insert table of Contents here).n
- \'2eend.n
- \'2eend_file.n.n
- .]
- .b(SEE ALSO:).n
- .end
- .rem(=================================)
- .rem( in macro topic )
- .rem(=================================)
- .ent(cmdin,\'2ein Macro,The )
- .b(SYNTAX:) \'2ein.n
- .n
- .b(EXPLANATION:) This .p1(macro) starts an indented text section,
- which usually contains a list of items. The indented section is
- a hanging indent, which means that the first line is indented less
- than the following lines. Each beginning line will look good if
- it begins with either a number or a bullet..n
- .n
- .b(EXAMPLE:).n
- .n
- .[
- \li720
- \'2eent(sellcars,Sell Cars,How to ).n
- \'2ein.n
- \'23n(1)Find a customer.\'2en.n
- \'23n(2)Convince them this is the car of their dreams, no matter
- how bad it is.\'2en.n
- \'23n(3)Close the sale. Get their John Hancock on the bottom line.\'2en.n
- \'2eun.n
- \'2eend.n.n
- .]
- .b(SEE ALSO:) .j(cmdun,\'2eun), .j(cmdpp,\'23\'23), .j(cmdpb,\'23b), .j(cmdpn,\'23n).n
- .end
- .rem(=================================)
- .rem( un macro topic )
- .rem(=================================)
- .ent(cmdun,\'2eun Macro,The )
- .b(SYNTAX:) \'2eun.n
- .n
- .b(EXPLANATION:) This .p1(macro) ends ('unindents') an indented text
- section..n
- .n
- .b(EXAMPLE:) See the example for the \'2ein command..n
- .n
- .b(SEE ALSO:) .j(cmdin,\'2ein).n
- .end
- .rem(=================================)
- .rem( pound pound macro topic )
- .rem(=================================)
- .ent(cmdpp,\'23\'23 Macro,The )
- .b(SYNTAX:) \'23\'23.n
- .n
- .b(EXPLANATION:) This .p1(macro) represents a bullet for a list
- item. It should be followed immediately by text..n
- .n
- .b(EXAMPLE:).n
- .n
- .[
- \li720
- \'2eent(advantages,Quilt Advantages, ).n
- \'2es.n
- \'23\'23Uses no electricity.\'2en.n
- \'23\'23All natural construction.\'2en.n
- \'23\'23Reduces number of blankets needed.\'2en.n
- \'2eend.n.n
- .]
- .b(SEE ALSO:) .j(cmdun,\'2eun), .j(cmdpb,\'23b), .j(cmdpn,\'23n).n
- .end
- .rem(=================================)
- .rem( pound b macro topic )
- .rem(=================================)
- .ent(cmdpb,\'23b Macro,The )
- .b(SYNTAX:) \'23b(text).n
- .n
- .b(EXPLANATION:) This .p1(macro) represents a list item that starts
- with a bullet and with the given .b(text) in boldface. It should
- be followed immediately by text..n
- .n
- .b(EXAMPLE:).n
- .n
- .[
- \li720
- \'2eent(glossary,Glossary, Keyboard ).n
- \'2es.n
- \'23b(Autorepeat)If held down a key will begin to send
- its code repeatedly.\'2en.n
- \'23b(Mode key)Modifier keys, used in conjunction with normal
- keys. Includes shift, control and alternate.\'2en.n
- \'23b(Scan code)A byte value or values sent to the computer.\'2en.n
- \'2eend.n.n
- .]
- .b(SEE ALSO:) .j(cmdun,\'2eun), .j(cmdpp,\'23\'23), .j(cmdpn,\'23n).n
- .end
- .rem(=================================)
- .rem( pound n macro topic )
- .rem(=================================)
- .ent(cmdpn,\'23n Macro,The )
- .b(SYNTAX:) \'23n(1).n
- .n
- .b(EXPLANATION:) This .p1(macro) represents a numbered list item.
- It should be followed immediately by text..n
- .n
- .b(EXAMPLE:) See the example for the \'2ein command..n
- .n
- .b(SEE ALSO:) .j(cmdun,\'2eun), .j(cmdpp,\'23\'23), .j(cmdpb,\'23b).n
- .end
- .rem(=================================)
- .rem( b macro topic )
- .rem(=================================)
- .ent(cmdb,\'2eb Macro,The )
- .b(SYNTAX:) \'2eb(string).n
- .n
- .b(EXPLANATION:) This .p1(macro) presents the given .b(string) in
- bold face type..n
- .n
- .b(EXAMPLE:).n
- .n
- .[
- \li720
- \'2eent(startup,Engine Startup, ).n
- Always ensure there is no gas fume build-up in
- the bilge. \'2eb(THIS IS VERY IMPORTANT.)\'2en.n
- Switch on the ignition and press the start button.\'2en.n
- \'2eend.n.n
- .]
- .b(SEE ALSO:) .j(cmdi,\'2ei).n
- .end
- .rem(=================================)
- .rem( i macro topic )
- .rem(=================================)
- .ent(cmdi,\'2ei Macro,The )
- .b(SYNTAX:) \'2ei(string).n
- .n
- .b(EXPLANATION:) This .p1(macro) presents the given .b(string) in
- italic type..n
- .n
- .b(EXAMPLE:).n
- .n
- .[
- \li720
- \'2eent(chars,Characters,Game ).n
- Your opponents in the game consist of \'2ei(trolls),
- rabid \'2ei(dogs) and defenseless \'2ei(kittens)..n
- \'2eend.n.n
- .]
- .b(SEE ALSO:) .j(cmdb,\'2eb).n
- .end
- .rem(=================================)
- .rem( [ macro topic )
- .rem(=================================)
- .ent(cmdob,\'2e[ Macro,The )
- .b(SYNTAX:) \'2e[.n
- .n
- .b(EXPLANATION:) This .p1(macro) marks the beginning of a region of text
- that will appear in a bold, fixed-width font. This is suitable for
- showing program examples or tables. NOTE: Since
- .p1(RTF) files use the open and close curly braces as part of their
- syntax, if you want to display them in your help file, you must
- 'escape' them by putting a backslash in front of them. This is shown
- in the example below..n
- .n
- .b(EXAMPLE:).n
- .n
- .[
- \li720
- \'2eent(progctl,Control,Program ).n
- The program is controlled with a message router:.n
- \'2es.n
- \'2ein.n
- \'2e[.n
- switch(wParam)\'2en.n
- \\\{\'2en.n
- \\tab case ID_OPEN: . . . \'2en.n
- \\tab \\tab break;\'2en.n
- \\tab case ID_CLOSE: . . . \'2en.n
- \\tab \\tab break;\'2en.n
- \\\}\'2en.n
- \'2e].n
- \'2eun.n
- \'2eend.n.n
- .]
- .b(SEE ALSO:) .j(cmdcb,\'2e]).n
- .end
- .rem(=================================)
- .rem( ] macro topic )
- .rem(=================================)
- .ent(cmdcb,\'2e] Macro,The )
- .b(SYNTAX:) \'2e].n
- .n
- .b(EXPLANATION:) This .p1(macro) marks the end of a region that was started with \'2e[. There should be a \'2e] for
- every \'2e[..n
- .n
- .b(EXAMPLE:) See the example for the \'2e[ command..n
- .n
- .b(SEE ALSO:) .j(cmdob,\'2e[).n
- .end
- .rem(=================================)
- .rem( n macro topic )
- .rem(=================================)
- .ent(cmdn,\'2en Macro,The )
- .b(SYNTAX:) \'2en.n
- .n
- .b(EXPLANATION:) This .p1(macro) is used at the end of a line, or on a line of its own, to indicate the actual end
- of the line. When \'2en is not used, separate lines are simply run together and used to fill whatever WinHelp
- window width the user has chosen..n
- .n
- .b(EXAMPLE:).n
- .n
- .[
- \li720
- \'2eent(drjnk,Health,To Your ).n
- This sentence will adjust itself to the.n
- width of the help window, since there is no.n
- \\'2en at the end of each line.\'2en\'2en.n.n
- This sentence will not adjust itself,\'2en.n
- since there is a \\'2en at the end of\'2en.n
- each line.\'2en.n
- \'2eend.n.n
- .]
- .b(SEE ALSO:) .j(cmds,\'2es).n
- .end
- .rem(=================================)
- .rem( s macro topic )
- .rem(=================================)
- .ent(cmds,\'2es Macro,The )
- .b(SYNTAX:) \'2es.n
- .n
- .b(EXPLANATION:) This .p1(macro) is used between lines to skip a space. If \'2es is used, then don't use \'2en.
- .n
- .b(EXAMPLE:).n
- .n
- .[
- \li720
- \'2eent(morjnk,Health,To My ).n
- This paragraph will be printed with the appropriate.n
- word wrapping and line wrapping. All parts of the.n
- paragraph will remain connected..n
- \'2es.n
- The \'2es above will separate this paragraph from.n
- the preceeding paragraph. The separation is slightly.n
- more than a single line spacing..n
- \'2eend.n.n
- .]
- .b(SEE ALSO:) .j(cmdn,\'2en).n
- .end
- .rem(=================================)
- .rem( end_file macro topic )
- .rem(=================================)
- .ent(cmdef,\'2eend_file Macro,The )
- .b(SYNTAX:) \'2eend_file.n
- .n
- .b(EXPLANATION:) This .p1(macro) marks the end of the macro file..n
- .n
- .b(EXAMPLE:) See the example for the \'2estart command..n
- .n
- .b(SEE ALSO:) .j(cmdstr,\'2estart).n
- .end
- .rem(=================================)
- .rem( brdrdb command topic )
- .rem(=================================)
- .ent(cmdbrdrdb,\\brdrdb Command,The )
- .b(EXPLANATION:) This command changes the border line style to a double line. It is used as a modifier to
- the \'2ebox command..n
- .n
- .b(EXAMPLE:).n
- .n
- .[
- \li720
- \'2ebox.n
- \\brdrdb.n
- This text will be displayed in a box with a double line border..n
- \'2ebend.n
- .]
- .end
- .rem(=================================)
- .rem( brdrs command topic )
- .rem(=================================)
- .ent(cmdbrdrs,\\brdrs Command,The )
- .b(EXPLANATION:) This command changes the border line style to a single line (this is the default). It is
- used as a modifier to the \'2ebox command..n
- .n
- .b(EXAMPLE:).n
- .n
- .[
- \li720
- \'2ebox.n
- \\brdrth.n
- This text will be displayed in a box with a thick border..n
- \\brdrs.n
- And this text will be displayed in a another box with a single
- line border..n
- \'2ebend.n
- .]
- .end
- .rem(=================================)
- .rem( brdrsh command topic )
- .rem(=================================)
- .ent(cmdbrdrsh,\\brdrsh Command,The )
- .b(EXPLANATION:) This command changes the border line style to shaded style. It is used as a modifier to
- the \'2ebox command..n
- .n
- .b(EXAMPLE:).n
- .n
- .[
- \li720
- \'2ebox.n
- \\brdrsh.n
- This text will be displayed in a box with a shaded border..n
- \'2ebend.n
- .]
- .end
- .rem(=================================)
- .rem( brdrth command topic )
- .rem(=================================)
- .ent(cmdbrdrth,\\brdrth Command,The )
- .b(EXPLANATION:) This command changes the border line style to a thick line. It is used as a modifier to
- the \'2ebox command..n
- .n
- .b(EXAMPLE:) See the example for the \\brdrs command..n
- .n
- .end
- .rem(=================================)
- .rem( li command topic )
- .rem(=================================)
- .ent(cmdli,\\li Command,The )
- .b(EXPLANATION:) This command changes the left margin indentation to the value that
- immediately follows the command. The value is expressed in .p1(twips).
- To reset the margin to its default, use \\li180..n
- .n
- .b(EXAMPLE:).n
- .n
- \'2e[.n
- \\li720.n
- \\ri720.n
- This sentence will be indented on the left and right margins by
- 720/1440 = 1/2"..n
- \'2e].n
- \\li180.n
- \\ri180.n
- .end
- .rem(=================================)
- .rem( ri command topic )
- .rem(=================================)
- .ent(cmdri,\\ri Command,The )
- .b(EXPLANATION:) This command changes the right margin indentation to the value that
- immediately follows the command. The value is expressed in .p1(twips).
- To reset the margin to its default, use \\ri180..n
- .n
- .b(EXAMPLE:) See the example for the \\li command..n
- .end
- .rem(=================================)
- .rem( ql command topic )
- .rem(=================================)
- .ent(cmdql,\\ql Command,The )
- .b(EXPLANATION:) This command changes the paragraph style to left justified. This is the default
- paragraph style..n
- .n
- .b(EXAMPLE:).n
- .n
- .[
- \li720
- \\qc.n
- This paragraph will have every line centered in the
- help window..n
- \'2es.n
- \\ql.n
- Now we are back to the default left justified paragraph..n
- .]
- .end
- .rem(=================================)
- .rem( qr command topic )
- .rem(=================================)
- .ent(cmdqr,\\qr Command,The )
- .b(EXPLANATION:) This command changes the paragraph style to right justified..n
- .n
- .b(EXAMPLE:).n
- .n
- .[
- \li720
- This paragraph is normally left justified..n
- \'2es.n
- \\qr.n
- And this paragraph is right justified..n
- \'2es.n
- .]
- .end
- .rem(=================================)
- .rem( qj command topic )
- .rem(=================================)
- .ent(cmdqj,\\qj Command,The )
- .b(EXPLANATION:) This command changes the paragraph style to fully justified..n
- .n
- .b(EXAMPLE:).n
- .n
- .[
- \li720
- \\qj.n
- The quick brown fox normally jumps over the lazy dog's
- back in a fully justified fashion..n
- \'2es.n
- .]
- .end
- .rem(=================================)
- .rem( qc command topic )
- .rem(=================================)
- .ent(cmdqc,\\qc Command,The )
- .b(EXPLANATION:) This command changes the paragraph style to centered lines..n
- .n
- .b(EXAMPLE:) See the example for the \\ql command..n
- .n
- .end
- .rem(=================================)
- .rem( tab command topic )
- .rem(=================================)
- .ent(cmdtab,\\tab Command,The )
- .b(EXPLANATION:) This command places a tab character in the macro and in the generated RTF file..n
- .n
- .b(EXAMPLE:) See the example for the \'2e[ macro language command..n
- .n
- .end
- .rem(=================================)
- .rem( 'hh command topic )
- .rem(=================================)
- .ent(cmdhh,\\'hh Command,The )
- .b(EXPLANATION:) This command allows you to put extended characters into a help file. Some commonly
- used extended characters are.n
- .n
- \tab\\'a9 => \'a9.n
- \tab\\'ae => \'ae.n
- \tab\\'bc => \'bc.n
- \tab\\'bd => \'bd.n
- \tab\\'be => \'be.n
- \tab\\'99 => \'99 (trademark symbol. This one may not work correctly, depending on the help compiler).n
- .n
- .b(EXAMPLE:).n
- .n
- .[
- \li720
- \\'a9 1994 Rimrock Software. All rights reserved.\'2en.n
- Distributed on 3\\'bd double density floppy disk..n
- .]
- .end
- .rem(=================================)
- .rem( glossary topic )
- .rem(=================================)
- .ent(glossary,Glossary, )
- .in
- ##.p(hlpcmplr,help compiler)
- ##.p1(macro)
- ##.p1(popup)
- ##.p1(project)
- ##.p1(RTF)
- ##.p(rtfcmds,RTF commands)
- ##.p1(template)
- ##.p(titlebar,title bar)
- ##.p1(toolbar)
- ##.p1(topic)
- ##.p1(twips)
- .un
- .end
- .rem(=================================)
- .rem( macro popup )
- .rem(=================================)
- .pent(macro,macro, )
- The replacement of a long series of .p1(RTF) commands with a single
- command word and (optional) series of arguments.
- .end
- .rem(=================================)
- .rem( template popup )
- .rem(=================================)
- .pent(template,template, )
- A series of text lines that constitute the minimal macro
- file that will convert to an RTF file and compile to a
- help file.
- .end
- .rem(=================================)
- .rem( project popup )
- .rem(=================================)
- .pent(project,project, )
- A file with the extension .HPJ, that contains options that
- specifies how a help file is to be built. Required by the
- help compiler.
- .end
- .rem(=================================)
- .rem( RTF popup )
- .rem(=================================)
- .pent(RTF,RTF, )
- Rich Text Format, a standard text file formatting standard. An
- RTF file consists of .p(rtfcmds,RTF commands) and normal text.
- .end
- .rem(=================================)
- .rem( RTF commands popup )
- .rem(=================================)
- .pent(rtfcmds,RTF commands, )
- Special commands in an .p1(RTF) file that describe how text is to be
- displayed. These commands start with a backslash (\\) character.
- .end
- .rem(=================================)
- .rem( help compiler popup )
- .rem(=================================)
- .pent(hlpcmplr,help compiler, )
- The program that creates a help (.HLP) file from the .RTF file,
- using the rules detailed in the .HPJ file.
- .end
- .rem(=================================)
- .rem( toolbar popup )
- .rem(=================================)
- .pent(toolbar,toolbar, )
- The line of graphical push buttons that are located directly
- below HelpGen's menu bar.
- .end
- .rem(=================================)
- .rem( title bar popup )
- .rem(=================================)
- .pent(titlebar,title bar, )
- The area at the top of the HelpGen program window that contains
- the program name, file name, system menu button and window size
- controls.
- .end
- .rem(=================================)
- .rem( topic popup )
- .rem(=================================)
- .pent(topic,topic, )
- A block of text in a help file that will be displayed as a single
- display page.
- .end
- .rem(=================================)
- .rem( popup popup )
- .rem(=================================)
- .pent(popup,popup, )
- A small window that appears when you select a topic with a dotted
- underline. The window will remain until you click the left mouse
- button again.
- .end
- .rem(=================================)
- .rem( twips popup )
- .rem(=================================)
- .pent(twips,twips, )
- A 20th of a point. There are 72 points in an inch, so there
- are 1440 twips in an inch.
- .end
- .rem(=================================)
- .rem( End of HelpGen macro file )
- .rem(=================================)
- .end_file
-