This content has been marked as final. Show 4 replies
First, thanks for all your help over the years with both RH and Captivate, and for the great hints at your site.
Second, I was *hoping* this option would show the nav pane link in the following case:
In my project I have set up a 2-pane window (Main_window) and a 1-pane window (CS_Window).
Main_window is used for calling Help from the toolbar button and some other places in the app when we want users to open help to the default topic.
CS_window is called from our app when a user presses F1 in a dialog (context-sensitive help). This window displays pertinent topic and toolbar but no nav pane. Just what I want.
Problem is, there is no way for users to access nav pane from the context-sensitive window. Related topics etc are all opened in this same window. In order to get more info, users have to close the help and re-open it via the toolbar or other link.
When a user presses F1, I would like them to see the "naked" topic, with a way to open the nav pane.
What is the best way to acheive this?
Is there a way to invoke a context-sensitive topic outside the WebHelp frameset so that this nav pane link will appear, and do what you describe?
Is there a way to add a button to my CS_Window that would re-open the topic in the Main_window, which includes the nav pane.
Other ideas? Suggestions greatly appreciated!
PS RoboHelp 7's own Help suffers from same problem: Click the Help button in a dialog, see the pertinent topic, but there is no way to find additonal info unless it is listed as a related topic. You have to close the Help window and invoke Help via the menu to see the nav pane.
You shouldn't have to mess with multiple windows; simply create one WebHelp output and let your developers do the heavy lifting.
You would generate the WebHelp with the "Show" link (which you can customize by using Rick's "Changing the 'Show' link appearance in all topics (WebHelp Only)" topic.
Note that you can also change the verbiage from "Show" to whatever, by replacing the "+sTitle+" string (including the two double quotes), so that your result is:
For CSH, the developers would call the topic's URL directly (target_topic.htm instead of start_page.htm#target_topic.htm). This would display the single topic pane only, with your spiffy new Show link available to open the full frameset version.