1.
That when you double-click on an index entry in the final documents, that the link can send you to a specific PART of the page that the link is to like you can in HTML. Example: I have a definitions page, I have the definition entries in the index (among all the other index entries). I would very much like it that my readers can double click on that index entry and go right to the definition.
2.
In the screen-capturing scenario rules lists and filter lists, the ability to COPY an existing rule and then modify just the part I want to change.
3.
More detailed HELP in the area of the screen capture scenario rules, filters and naming rules.
4.
Callout bullets that can have multiple connector lines to the application. However, admittedly, the appearance of the "control rectangle" in the specific documentation for THAT area being pointed to by the bullet, makes this less important. However, I did encounter times when ONE bullet would have been best, to point out multiple parts of the screenshot. This one deserves some design thought. Possibly a special kind of "bullet"?
5.
A way to select several words in text that comprise a proper noun and cause those words to never be separated onto two different lines (this is an important grammatical rule for professional documents). I ended up accomplishing this by doing a document-wide Find for the proper nouns I was looking for and then manually replacing them with an HTML snippet that accomplished the task. Specifically:
<NOBR>whatever text needs to all be on the same line here</NOBR>
Since there weren't very many, this was, in reality, almost as quick as a "Find and Replace" where the replace option may embed a style.
Unfortunately, this text does not (yet) get output into the PDF output format. Hopefully it will in upcoming versions.
6.
A way to do the same for text in variables (have all words always appear on the same line).
7.
A way to do the same with the "Find and Replace" feature.
8.
A BACK button in the Content Editor so that when you Ctrl + Click to follow a link to another page, that you don't have to remember what page you came from. This would be useful in other contexts as well, such as when you needed to fix something on another page and then "come back" to where you were working before.
9.
That the index that is delivered in CHM files also be published at the end of the PDF file (with links, or if there is more than one link, listing page numbers where multiple links would have lead to, with links on each page number). Now that I think of it, if it was me, I would go one step further and do this:
index_item_with_multiple_links
{Page title}, page N <- linked to page N
{Page title}, page N <- linked to page N
{Page title}, page N <- linked to page N
{Page title}, page N <- linked to page N
{Page title}, page N <- linked to page N
This way no links would get lost! :-)
10.
It would be really nice to have a logical text export of the keywords display, where the exported text would show the hierarchy as well as the connected topics. If there is a standard format for indexes, great. If not, permit exporting to a text file with hierarchy indicated by leading TAB characters, and also add the feature to import a keywords list from text file, to enable users, such as myself, to edit my index in a text editor, or to partially automate the task with another tool (which I or someone else might create).
11.
The ability to have an option in the FIND dialog box that says: "Index All Occurrences of this string".
12.
Microsoft HTML Help Workshop provides a way to make a "See Also" index entry jump to another keyword in the index. This capability would be nice to also have in Dr.Explain, because I encountered several places in my own project where I could have used this productively.
13.
Even though the ability to alter the
Project settings
Text Strings
Headers
"The contents of:" <TOPIC>
is nice, it doesn't solve everything.
Depending on the page name and the context, the "Contents of {Page Name}", which is great for MOST of my pages, is not always an appropriate heading over the links to the subtopic pages. For this reason, it would be VERY nice to be able to specify a custom string for this heading, perhaps in the "Properties" area in the lower-left of the project. This would enable the user to specify additional types of headings for THAT PAGE ONLY, like this:
{Page Name} Details
where {Page Name} is not at the end, but could be embedded in the middle of the string, or
More Details:
or just
Details:
where {Page Name} does not appear at all. This would be very nice, and would have solved a few problems for me in creating my help file.
14.
A Tasks management tab that lists every place in the text of the project where the term "TODO:" shows up (case insensitive), similar to that provided in many professional Integrated Development Environments (IDEs).
15.
There does not seem to be a way (yet) to edit the custom dictionary from within Dr.Explain. I know that I can edit it with Windows Notepad, as long as I carefully keep the separation characters following each word, but it would be safer in the long run if editing it could be done from within Dr.Explain for all the reasons one might want to edit a custom dictionary (for me, I occasionally add a word that I later decide shouldn't be in the custom dictionary, that I want the spell checker to start "marking" as a possibly-misspelled word again).
