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.
Goldberg, Steve (sgoldberg -at- elcom -dot- com) asked:
>I have context-sensitive help in a Windows-based application involving
>Help buttons on several dialog boxes. Each button is mapped to the
>specific help topic ID number. The question is does the WinHelp compiler
>change these ID numbers each time the project is compiled? In other
>words, if I add or delete a topic or topics, do I then have to re-map the
>links from the buttons to the (new) ID number?
Steve, the WinHelp compiler does not change the context ID numbers
FYI: On my current project, I've noticed that Doc-To-Help changes the
context IDs during it's conversion process when I've added new material
to the middle of a section. This has caused me problems with linking,
so I've had to check this carefully.
On previous RoboHelp projects, I never had a problem with this - the
context IDs were static once assigned (I always had RoboHelp generate
the map files). Occaisionally, RoboHelp duplicated context IDs in the
map files, which generated an error during the compile. It dup'd both
the context string and the ID - I just deleted one of the two lines in
the map file and everything worked OK.
kcramer -at- ncslink -dot- com
Sr. Information Developer
NCS Education, Mesa AZ