|
|
Post by Stefan on Apr 25, 2021 6:08:03 GMT -5
... "Ambiguous Command? Prefix with 'L' (Line), 'P' (Primary) or 'W' (Working With) "
and what should I do to effectively 'prefix' the command I was looking for?
Possible HELP indexing error? Or is HELP searching the 'document text' for the word 'action' and find lots of occurences?
Example: HELP ACTION
|
|
|
|
Post by George on Apr 25, 2021 10:26:45 GMT -5
Stefan: Beat me up, it was a missing entry on the Help Index table.
No, SPFLite does not search the CHM file.
If you want to volunteer to review and match-merge the Help Index and the HelpNDoc topic equates, I'll send you the files, so we don't encounter any more 'missing' entries.
I thought the ambiguous message was sufficiently clear, it appears whenever the user's search term could not be found. For example HELP UC - does the user want the Primary command or the line command? The suggestion is to prefix it with a "P" or an "L". Making it HELP PUC or HELP LUC. I'm open to suggestions for rewording it.
George
|
|
|
|
Post by George on Apr 25, 2021 14:43:14 GMT -5
Robert: It would be nice if we could get some proper Help searching, but I've looked at adding keywords etc. to the HnD files and it is a ridiculous amount of work. You have to go through each and every page manually, locate the words that you think might be the ones people would search for, hi-light them and click to add to the Keyword list.
But before that you have to determine your Keyword list structure. i.e. the hierarchy of how keywords are arranged. And if you have a hierarch, each of these clicks above means selecting where in the hierarch you want it to appear.
And as you are aware, with over 1000 pages of documentation, this is just a short afternoon's work.
George
|
|
|
|
Post by George on Apr 25, 2021 15:52:43 GMT -5
Robert: I just, last release, cleaned up all the Primary and Line commands. And there's so few collisions (like UC) that I'm simply not going to get into adding operands to HELP. I mean really, regardless of what you enter for a HELP operand, you end up in the CHM Help flag, how hard is it to navigate to what you're looking for?
This is one of those "wouldn't it be wonderful if ... " things. Yes, in a perfect world, all this stuff would 'just work', but frankly this is not what I want to spend my remaining programming effort doing. Typing is becoming increasingly difficult, and improving Help indexing is at the bottom of my list.
George
|
|
|
|
Post by George on Apr 26, 2021 8:36:21 GMT -5
Robert: Sorry, I wasn't asking for help as to how to prefix commands, I was trying to explain the existing message Stefan got which suggested prefixing the ambiguous commands (like UC). Maybe this will explain the problem. Given the following file from HelpNDoc, which provides equates for the 300 odd Help topics. When you enter HELP XXXX, somehow we have to get from XXX to one of those numerical equates. I have a simple table of XXXX strings, each with their associated equate. Come up with suggestions to improve on this and I'll stick it in. George _HnD.inc (5.61 KB) |
|
|
|
Post by George on Apr 26, 2021 14:06:10 GMT -5
Robert:
Another example:
The samples here show the entries for the Primary and Line command versions of the UC command and the Primary FIND command
Here's a few lines from the HnD file, this file is simply #INCLUDE'd into the compile of SPFLite, so those Equates become available throughout the compile.
' Project: SPFLite - V2.4.21090 2021-03-31
' Generated by HelpNDoc - https://www.helpndoc.com
%HELP_LUC = 74
%HELP_PUC = 150
%HELP_PFIND = 103
And here's the lines from the SPFLite Help table setup; the left entry is matched to the HELP XXXX operand; the right entry is passed to the CHM viewer to open CHM at the correct topic
GetHelpInit1("LUC", %HELP_LUC)
GetHelpInit1("PUC", %HELP_PUC)
GetHelpInit1("FIND", %HELP_PFIND)
So if you just say HELP UC, the search fails because it only has the two variations PUC and LUC. If you say HELP FIND, no problem, it is found and resolved properly.
Just remember at execution time there is no access to the string %HELP_LUC or %HELP_PUC because they are SOURCE statements.
|
|
|
|
Post by George on Apr 27, 2021 8:43:05 GMT -5
Robert All those GetHelpInit1 calls are coded, by me, to match what operands people would normally enter, and the HnD created equates.
The whole collection of about 300 of those GetHelpInit calls is executed at Startup time to build the table that is searched when you say HELP XXXX.
As I said painful, manual coding.
George
|
|
|
|
Post by George on Apr 27, 2021 10:59:37 GMT -5
Robert: 1. The %HELP_ is fixed by HnD, the part after the _ is specified in the Topic Properties in HnD. The associated topic number is normally assigned by HnD, there is an input box for it in the Properties dialog, but I've never altered what's there. 2. The whole file is just as it comes from HnD, no changes are made. HnD "knows" about PB and how to create a valid INCLUDE file. Please don't suggest altering all the HnD Topic ID's unless you've come up with some amazing procedure. It means going through the following for each topic in the document. - Select topic in Left column
- Select Topic properties from the Ribbon bar
- Edit the HelpID text box
- Enter
George |
|
|
|
Post by George on Apr 27, 2021 13:43:45 GMT -5
Robert: I can manage the HnD editing, it's boring grunge stuff, but it can be done in a couple hours.
Show me.
George
===> OK, I will get started, look for the email late today or early tomorrow - R
===> Update: Specs in progress, hope to be done sometime today - R |
|
