Adobe Community : All Content - All Communities

Disappearing screen elements in Responsive HTML 5 output

forums_noreply@adobe.com — Thu, 06 Nov 2014 14:29:28 GMT

I recently installed the update to RoboHelp HTML 11, which was supposed to fix a lot of problems with Responsive HTML 5 output issues. However, a new issue has just cropped up out of nowhere and I have no idea why it's happening.

When I generate Responsive HTML 5 output for my help system, the following items are missing from the screen in the browser:

- The vertical separator bar that separates the TOC from the help content window

- All the "hover" buttons (the dark versions of the TOC, Search, Glossary, Home, and Print buttons that appear when you hover over them or when that page is selected)

Also, the Show/Hide button is visible (even though the separator bar is not), but it does not function at all.

The output was generating just fine, with no such problems, until just a couple of days ago. This struck out of nowhere. Does anyone have a clue what is causing this or how to fix it?

Thanks!

Tim Huddleston

Disappearing screen elements in Responsive HTML 5 output

forums_noreply@adobe.com — Thu, 06 Nov 2014 15:30:08 GMT

When I generate Responsive HTML 5 output for my help system, the following items are missing from the screen in the browser:

- The vertical separator bar that separates the TOC from the help content window

- All the "hover" buttons (the dark versions of the TOC, Search, Glossary, Home, and Print buttons that appear when you hover over them or when that page is selected)

Also, the Show/Hide button is visible (even though the separator bar is not), but it does not function at all.

The output was generating just fine, with no such problems, until just a couple of days ago. This struck out of nowhere. Does anyone have a clue what is causing this or how to fix it?

Thanks!

Tim Huddleston

Can I make image map hotspots visible?

forums_noreply@adobe.com — Fri, 21 Mar 2014 14:25:00 GMT

I have created an image map with multiple hotspots (using RoboHelp HTML v11, creating a WebHelp help system). The hotspots are invisible by default. Is there any way to make them visible, so the user can see that they are present in WebHelp? Thanks!

Tim Huddleston,

Charlotte, NC

Why does paragraph formatting change when help is published?

forums_noreply@adobe.com — Mon, 03 Feb 2014 15:29:31 GMT

I'm running RH11 on Win7 Pro and creating a help system in WinHelp format. When I save and generate my help system and view it from my local drive, it looks fine. However, after I publish the help system to a network drive, any numbered/bulleted paragraphs have been moved to the left...sometimes so far that the number or bullet is off the left edge of the frame.This happens both when I use the Publish command to publish the help files to the network drive AND when I copy the contents of the !SSL!/WebHelp folder to the network location.

Can anyone explain why this is happening and what step(s) I can take to fix the problem?

This is urgent!!! I'm on a deadline!!!

Thank you!

Tim Huddleston

Charlotte, NC

Linked PDFs do not open in AIR help window

forums_noreply@adobe.com — Thu, 09 Jan 2014 18:24:35 GMT

I am creating a help system in RoboHelp 10 and outputting it as AIR help. The help topics include links to several PDF documents, which are stored locally (they are not on a server or Web site). When I click any of the links in the AIR help window, however, the window goes blank; the content from the PDF does not appear. No other windows open, either. How can I get the content from the linked PDFs to appear in the AIR help window? Thanks!

Default font in AIRHelp's left-hand nav pane?

forums_noreply@adobe.com — Thu, 16 Jan 2014 21:09:42 GMT

This may seem like a strange question, but does anyone know the name of the default font that is used in the left-hand navigation pane of the AIRHelp window? I'm talking about the AIRHelp window that you install on the user's PC, not the browser help. Any ideas? I'd like to match it and can't figure out which font it is.

Thanks!

Tim