|
|
Post by Robert on Feb 7, 2023 13:56:40 GMT -5
The command HELP EFT does not work as one might expect. It does not bring up the EFT help, but rather shows the default help entry, depending on whether you asked for the help from FM or an edit tab.
If you ask for a fully-specified HELP EXTENDED FILE TYPES it will work, but that is more wordy than should be required.
HELP EFT is a reasonable HELP request, and should work without spelling it out.
|
|
|
|
Post by George on Feb 7, 2023 14:21:36 GMT -5
Checked the HnD file. Yep, one of the Topic Properties had a - instead of a _ between keywords.
Will be picked up next release.
Thanks for reporting it.
George
|
|
|
|
Post by Robert on Feb 17, 2023 13:29:06 GMT -5
As of 23.047, this fix is not in. Is that because you only regen the Help on releases, not Betas?
Of course it is. Chalk it up to dead brain cells.
|
|
|
|
Post by George on Feb 17, 2023 13:58:00 GMT -5
And here's why the Doc only gets done for full releases.
This is an exerpt from the checklist for a new release. I definitely need this nowadays with my memory in old fogie mode.
Prepare the Documentation
1. Verify the _SPFVersion.INC and _CFGVersion.INC files have the correct (and same) Version # and date.
2. Edit \Docs\SPFLite2.HnD with HelpNDoc. Ensure all doc is updated to reflect new or changed support.
3. If new topics were added, ensure the Topic ID is formatted with reasonable keywords. The 1st letter indicates the Help section (Intro, Working with etc.) followed by keywords separated by underlines. For example, a new topic about a new BlahBlah function would be W_BLAHBLAH_BLAH which sets up pointers for 2 Kwds BLAHBLAH and BLAH. If a topic ID has an embedded _ character (Like macro functions) then double the _. e.g. F_Get__Arg$
The main topic title should also be meaningful, as all its words become Kwds as well.
4. Adjust the version and date in the document header. Obtain this from the current _SPFVersion.INC file
5. Process and create the SPFLite.CHM, SPFLite.PDF and the \SPFLite\HTMLS folder.
6. Use the HnD menu item Generate Help => Code Generation => Delphi/Pascal Unit to create the HnD topic index. Save this file in \SPFLite2\Resource File\HnD.pas
7. Execute \SPFLite2\Resource Files\BlB2Txt.exe. This will populate \Resource Files\Text with the full raw text from the newly created CHM file.
8. Execute \SPFLite2\Resource File\HnDFormat.exe. This will process the HnD.pas, and the text files in \Resource Files\Text and recreate the \Resource File\HnDIndex.txt, which is distributed with the SPFLite2 Install file. It takes a while, wait for the “Done” message. This is the whole singular purpose for step 3 and steps 6 thru 8.
9. Copy the HnDIndex.txt file to the main SPFLite2 folder, and place another copy in the /SPFLite/Distribution folder.
10. Compress the PDF file using Advanced PDF Compressor, ensure image processing is set to color, 100% resolution.
11. Copy the SPFLite.CHM and SPFLite.PDF files to \SPFLite2\Distribution folder.
|
|
