Context Sensitive window not showing navigation pane

This forum is for all Flare issues related to the Microsoft HTML Help target.
This target produces "CHM" files in the output.
Post Reply
Graham Campbell
Propeller Head
Posts: 54
Joined: Tue Oct 30, 2007 4:40 am
Location: Glasgow, Scotland, UK

Context Sensitive window not showing navigation pane

Post by Graham Campbell »

I have four skins in my project: DefaultWindow, IndexWindow, SearchWindow and ContextWindow. The first three work perfectly.

The ContextWindow skin is used to display our context-sensitive help topics, when users press F1 or the associated Help button on modal dialogs in our application. It isn't behaving properly at all.

It doesn't show the navigation pane properly:
context_window.png
What is shown is an unlabelled Index search tab, which works but isn't what I asked Flare to include in the build:
context_window_features.png
The Window never displays itself where I've told it to, and is consistentely displayed the wrong size.

I've tried deleting the skin and creating a new one, but that didn't work. I thought it might be a Vista issue, but building on XP produced the same problematic window.

Any assistance would be much appreciated.
You do not have the required permissions to view the files attached to this post.
Graham Campbell
Propeller Head
Posts: 54
Joined: Tue Oct 30, 2007 4:40 am
Location: Glasgow, Scotland, UK

Re: Context Sensitive window not showing navigation pane

Post by Graham Campbell »

I should also note that when I click "Preview as HTML Help Window" in the Skin Editor, it shows up exactly as I expect it to.

Only in the built CHM does it misbehave.

Also, I should mention we're all using Flare 5 in the office. I just tried rebuilding the help in Flare 4.2 and it works perfectly. This appears to be a Flare 5 HTML compilation bug. Anyone else suffering this?
Graham Campbell
Propeller Head
Posts: 54
Joined: Tue Oct 30, 2007 4:40 am
Location: Glasgow, Scotland, UK

Re: Context Sensitive window not showing navigation pane

Post by Graham Campbell »

Turns out there's a patch that resolved this issue for me.

Shame I didn't know about the patch before contact MadCap support by raising a bug, but at least the issue was resolved.
Post Reply