TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:Checking Application HTML Help Context IDs From:Peter Lucas <peterlucas -at- decadesoftware -dot- com> To:TECHWR-L <techwr-l -at- lists -dot- raycomm -dot- com> Date:Fri, 20 Feb 2004 10:58:46 -0800
(This is not exactly related to technical writing, but there are folks here
who create HTML Help. If there's a better list for this question, please let
me know.)
Our company for years has created WinHelp help files using ForeHelp.
ForeHelp came with a great utility called QuickFix that would run in the
foreground and intercept the F1 call from any application to the
corresponding WinHelp file. So, if we had a field on a form in our product,
and I needed to know the field's context ID, I could just press F1 and the
QuickFix dialog would display the help file name, the context number, and
the topic name.
We are now creating our help using Microsoft HTML Help, but I can't seem to
find a similar utility. The product we are using, RoboHelp for FrameMaker,
doesn't have a similar utility, and the folks at RoboHelp don't have any
idea where I could find one.
Yes, I know I can just get the list of IDs from the programmer, but
sometimes even with the list, I get errors for certain fields, and with
QuickFix, it was easy for me to tell whether the ID had been assigned
incorrectly by the programmer, or whether I had forgotten to assign the ID
to the topic.
If I need to, I can have one of my programmers here come up with something
that intercepts the call to the HTML Help API, but I'd rather not have them
reinvent the wheel, so to speak.