Problem #1:
I've seen several items in this forum for creating a button on the toolbar that would open a web page or a topic in the project. I've created the button and tried many things in the OnClick area but I cannot get it to open a topic in the project. I've been able to make it display a blank topic when the button is clicked...there's something missing or wrong, obviously, in the javascript syntax I'm using. (I don't know javascript at all; I'm just trying things based on what I've found by Googling and by searching this forum.)
Among the many things I've tried are:
window.top.body.location='href=..\Content\Common_Files\How_to_use_Help.htm'
window.top.body.location='href=C:\Help for Builds\test web\Output\WebHelp\Content\Common_Files\How_to_use_Help.htm' (do I need the full path to the file?)
window.open('C:\WebHelp\How_to_use_Help.htm') (tried a shorter path)
and many other variations
Can anyone tell me what the javascript should be? TIA!
Problem #2
In the Index and TOC, when I scroll over the text of the items, they turn red. I'd like to use a color that fits better with the skin but can't find where this is set.
customizing WebHelp skin
Re: customizing WebHelp skin
For anyone else doing this, what worked is:
window.open("../Content/Using Help.htm","_blank", "resizable=1,width=300,height=300")
where "Using Help.htm" is the topic file I'm opening. The path depends on where your help is installed; I put the files I wanted to call from buttons at the Content root (no subfolder) just to make the path short.
window.open("../Content/Using Help.htm","_blank", "resizable=1,width=300,height=300")
where "Using Help.htm" is the topic file I'm opening. The path depends on where your help is installed; I put the files I wanted to call from buttons at the Content root (no subfolder) just to make the path short.
Re: customizing WebHelp skin
Have a look here...jpeffley wrote:Problem #2
In the Index and TOC, when I scroll over the text of the items, they turn red. I'd like to use a color that fits better with the skin but can't find where this is set.
http://kb.madcapsoftware.com/Default_CSH.htm#OUTW1018F
Re: customizing WebHelp skin
Has anyone tried this in 5.0? I made the suggested changes to the TOC and Index files from the KB article - this worked in 4.2. I made the exact same change in the files in 5.0, and it seems to have no effect on the output. I can get still get rid of the red hover color by regenerating in 4.2 - so it's a workaround for now, but I'd rather just work in the one version. Any help appreciated. thanks.
Re: customizing WebHelp skin
I created a new style for a toolbar item called 'Pdf', and I want the button to open a PDF file. I tried the suggestion for the javascript posted here (thank you!), but when I build the project, I get the error message 'Object reference not set to an instance of an object'.
The error occurs when I add the Pdf button to the Webhelp Toolbar buttons list and try to build the file.
Any suggestions?
Thanks!
Karen
The error occurs when I add the Pdf button to the Webhelp Toolbar buttons list and try to build the file.
Any suggestions?
Thanks!
Karen
Re: customizing WebHelp skin
When you added the item for the toolbar, did you specify a tooltip or label? In one or both of those, there's a bug if you try to delete everything in the field. You have to leave at least a space or a period or something in the field(s).
Lisa
Eagles may soar, but weasels aren't sucked into jet engines.
Warning! Loose nut behind the keyboard.
Re: customizing WebHelp skin
Yep, I defined both a tooltip and a label.
Thanks!
K
Thanks!
K
-
RoyTheWriter
- Propeller Head
- Posts: 20
- Joined: Fri May 29, 2009 8:18 am
Re: customizing WebHelp skin
I've been able to change my accordion item hover color in the Skin in 5.0. Open the Skin Editor>Styles>AccordionItem>Font>BackgroundGradientHover and then select how you want that to look.dlogan wrote:Has anyone tried this in 5.0? I made the suggested changes to the TOC and Index files from the KB article - this worked in 4.2. I made the exact same change in the files in 5.0, and it seems to have no effect on the output.