Webhelp opening in a new window

[dhall]

Hi:

I have had to reinstall MadCap flare (to 4.2) and Analyzer (to 2.3) on my computer.
Since doing this, the MadCap products seem to publish Help OK, however, once published, we access 7 dfiierent Halp systems published using Mapdap.
The 7 Help systems are all access inside Frames in an ASP.NET app.

The issue I am having is that I can launch the first Help system in its frame, but any Help I launch afterward will launch in a new pop-up window.

Can anyone be of assistance with this issue?

Regards

[RamonS]

When making subsequent calls you need to specify the window name so that the browser knows in which window to display the help. There was a thread about this in the forums that pointed out that the window name isn't the one you might think it is. Now, if I could just remember....

Yay! I found it, see here: http://forums.madcapsoftware.com/viewto ... &sk=t&sd=a

[dhall]

Thanks for the reply Ramon5, however, this is not the same issue.

For our menu links we use an XML file that identifies the frame to load help.
Publishing with Flare 3.1 does not have this same issue.
I have found 4 major issues in Flare 4.2 and identified them and my solutions to overcome them below:

1.Publishing help with Flare 4.2 causes new windows to open rather than having it open in the target frame.
• The solution was to Re-activate Flare 3.1 and publish with it.
2.When using the shortcut methods to link content to the TOC in Flare 4.2, if a topic was linked to a file used elsewhere (i.e. under construction page), the TOC would jump to another topic that shared the same file.
• The solution was to link topics in th etopic properties panel rather than right-click and link topic.
3.When re-importing documents, Flare 4.2 creates a new version of the image files (example: image.gif gets a duplicate named image1.gif and so on).
• The solution was to re-import and use Analyzer to clean up the links, then delete the extra files in the image folder.
4.When publishing with Flare 4.2, the Help systems are very slow to load.
• The solution was to publish with Flare 3.1

Regards