A general question on this topic - I was hoping to use the Favourites tab in a CHM file as a method of asking reviewers to look at specific topics rather than reviewing an entire CHM file.
However it isn't working because as soon as I copy the CHM (even on my own PC) the Favourites tab is cleared.
Do you know if there is a way of changing this behaviour? (eg a "Do not flush Favourites" check box somewhere).
Cheers + thanks in advance.
I don't know if Pete follows these forums anymore so let me step in. As Pete stated, the CHM favourites are stored in the HH.DAT file. The issue here is that this is a PC specific file which stores lots of data about CHM file usage. In theory it could be copied to each PC, but in practice this would cause all sorts of other issues. For example, if the user had used the Favourites functionality on a different CHM - maybe even one not controlled by you - copying the HH.DAT file to their PC would delete that favourite.
So in summary, this file is best left well alone. There is a post I wrote about this file at: http://www.cmcandrew.com/robocolumn/the-hhdat-file/
Thanks for that.
Drat etc - looks as though this really isn't an option then.
What a shame, because that would have been a neat way of seeking comments on a selection of topics in a huge help system.
Andy if it is just reviewing topics you require, RoboHelp has some cool features in the newer releases. You don't say what version you have, but now you can even select topics, output to a PDF, have a reviewer add comment to the PDF using the free Acrobat Reader, and you import them in to your project and accept / reject the same as in Word.
I just had a look at that PDF For Review function, and yes it does as you rightly say.
However, I'm still left feeling mildly unsatisfied because the other aspect of the CHM approach that appealed was that if keen reviewers felt so inclined, they could have merrily drifted off into other parts of the help system via "related topics" links and Index entries etc. Whereas here they are ultra confined to reviewing the range of PDF'd content only. Arguably there are benefits to that of course, but there are also benefits to having folk "play around" in the help.
I had a thought along the lines of distributing a simple html doc with the CHM that inked in to specific topics in the CHM. But although technically feasible, I'm already starting to recoil from this approach too.
And so it continues...
Another way you might consider listing a group of topics easily would be to implement a See Also. The process is really straightforward. You open the See Also pod, define a keyword, then associate topics with the keyword.
Then you add a See Also control to any topic you like. (You can call it Favorites if you want) The net result is that the viewer looks at the topic with the See Also control, clicks the control and sees the list of topics to be viewed. You could also copy the control and paste it into each of the topics that are part of the list so that they can easily move from this topic to the next.