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: index and compile problems in RoboHelp From:"Glenn Maxey" <glenn -dot- maxey -at- voyanttech -dot- com> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Wed, 20 Jun 2001 12:43:24 -0600
> -----Original Message-----
> From: Sean Hower [mailto:hokumhome -at- freehomepage -dot- com]
> Sent: Wednesday, June 20, 2001 12:24 PM
> To: TECHWR-L
> Subject: index and compile problems in RoboHelp
>
> First, when I compile a project in the RoboHelp Explorer, and
> try to run the project from the RoboHelp Explorer, an older
> version of the help appears. If I open the help file from
> Windows Explorer, the newest version of the help appears.
RoboHelp isn't running the true help engine. It is running an emulator.
Hence, it isn't going to have all of the functionality and will appear
different. IOW, not a problem.
> The second problem is a little more serious. I am creating an
> index in the same help project. When I save and compile the
> project, I get the same problem stated above. When I use
> Window Explorer, however, the newest version of the help file
> appears, but the index remains unchanged.
Combination of the RoboHelp emulator and leftover GID files.
Whenever you start a help file for the first time (outside of RoboHelp),
the help engine creates a GID file based upon the CNT file and the
keywords used in the index. The file hangs out and isn't regenerated,
and thereby speeds up the starting of subsequent calls to the help
system.
Hence, whenever you change your help file or CNT file, blow away the GID
file and force the help engine to regenerate it. You can blow away all
GID files on your system and it won't hurt anything. They'll be
regenerated when needed. If you don't delete the GID file whenever you
do a change, you'll get old info in the Contents or Index.
Glenn Maxey
Voyant Technologies, Inc.
Tel. +1 303.223.5164
Fax. +1 303.223.5275
glenn -dot- maxey -at- voyanttech -dot- com
*** Deva(tm) Tools for Dreamweaver and Deva(tm) Search ***
Build Contents, Indexes, and Search for Web Sites and Help Systems
Available now at http://www.devahelp.com or info -at- devahelp -dot- com
Sponsored by Cub Lea, specialist in low-cost outsourced development
and documentation. Overload and time-sensitive jobs at exceptional
rates. Unique free gifts for all visitors to http://www.cublea.com
---
You are currently subscribed to techwr-l as: archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.
