This content has been marked as final. Show 5 replies
Can I clarify that what you want is a button on the toolbar of a merged webhelp setup that calls another webhelp output?
Furthermore, the target webhelp output is in fact part of the merge?
Is that the case? If so I think I can see how to do and will look into in the morning. I'm intrigued by the logic of doing it this way though.
I found the solution--on the RoboWizard' site (Rick Stone). In the "Skinny on Skins" file, he has a topic "Add Toolbar button to invoke File" that I adapted, with some modifications, for my dilemma.
And yes, the "help" WebHelp is part of the merged files. The merged "help" WebHelp has its own folder in the folder structure, just like any other part of the merged file, and is written to the Generated folder and Published folder structure exactly the same way as other merge files do. It's just linked to the Skin instead of the TOC.
I had already created a help button in the skin to link to, so that was no problem.
What I couldn't get the "help" WebHelp to do was link it to the button, and make it open in a new window! There seemed to be nowhere to add a "frame=_blank" instruction.
Note: The above links to the merged, generated project, on my PC in the folders Robohelp creates to store each portion of the project after merging.
I still have to figure out how to make a relative link work for the LAN location, and the server. The server location will be easier, because it will be a straightforword HTTP call, instead of the file:///blah blah thing :-) I have to be able to demo without going to the server location--that's why the disk-based file.
If you have suggestions for the relative link, that would be great. I've tried various combinations for the "file://:" call, but it hasn't worked properly. It's been about 5 years since I've done anything like this, and I just don't remember how I did it before....
That's what I was going to point you at when you confirmed that you were trying to do what I thought.
I was also going to add the next bit. You should just need the relative path from the parent project to the start page of the child. Something like
Post back if that doesn't work.
When you stated the relative link as:
I figured out there should be a dot (.) in front, with a slash, like this:
I tried two dots .. first, but that took the link too far up in the directory--one step up is one dot :-) which is what I needed.
Thanks so much Peter!
Now if I can get relative links from one merge file (child) to another to work, I will be all set.
Child / child links are covered in my topic on merged webhelp. They're easy.