yes I apologize, "hlp" was a typo. It should read as "help."
I did follow the article, but again I do not see where that
plays a part for us in particular. While it is the ideal way to run
the robohelp system, I do not necessarily think that it applies in
our situation. Certainly there are exceptions to the "rule,"
correct? Is there not a more straightforward answer for my
originial question, than the now repetitive "roboengine" answer? I
apologize if I sound trite, but I am getting the feeling that my
point is getting miscontrued or lost.
This is what we want you to see when you pull up the help
system (from any given page within the application) in our
situation:
Scrreenshot
1
This is what you will currently see when you pull up the help
system (from any given page within the application) in our
situation:
Screenshot
2
These screenshots reflect one particular page I used to show
the example. So you can see in the screenshots, that the help
system is pulling up the appropriate page related to the content in
the application. It is just not reflecting that page's location in
the TOC. I feel inclined to also mention that our context ID's are
set up properly. On the application side, the context ID's that the
help system looks for in our application pages, are hardcoded into
the application. Maybe this is why we are not using roboengine.
Whatever reason we have for doing this, it is ours and that is what
we are doing currently "like it or leave it."
If the "roboengine" answer is the solution for our problem,
then I would greatly appreciate it if you could quote where in
Rick's article it addresses the issue I am facing currently as
described above as well is in my screenshots. I have read through
the article, but nothing is jumping out at me, as to a solution for
the current issue.
Thanks again for your time and patience.