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:Re: help on help From:Roger Mallett <roger -at- CSICAL -dot- COM> Date:Thu, 8 Oct 1998 07:03:18 -0700
>Using WTHC, you can take ANY .exe file on your system (that is, any
>Windows
32--bit application), and it will build a context-sensitive help file .
>. .
>
>You can then create the language for the c-s help on each field and
>button,
>compile the help using WTHC, and run the application (the .exe file)
>with
>the embedded c-s help. It's actually quite neat. The c-s help file can
>be a
>separate file, or it can be incorporated into a more comprehensive
>full-help project.
While the process of writing What's This help for someone else's program
is easy, it is not so easy to display the topics. The application
calling the What's This help must make a call to RoboHelp's csh.dll in
order for the help What's This help to display. So, while you may get
experience using the RoboHelp tool without programmer intervention, you
won't get to see your topics in action until you have a program that
makes the call to the dll.
