Error message while opening help file in the application

[Olanko]

When I try to open my HTML Help in the application the following error mesage appears:
\"The window name \"main\" passed to HH_GET_WIN_TYPE has not been specified.\"
But after you close this message the help file opens without problems.

What should I change to get rid of this message?

Thanks.

[paulblusas]

Interesting.

I am now getting this too for some hyperlinks in my built projects - but never did before. Apart from the message appearing the help appears to work fine. Looks like another support ticket needs to be raised...

[Olanko]

It seems I resolved the problem.

The fact is that in order to call Help file the developer uses HH_GET_WIN_TYPE command which looks as follows:

HH_WINTYPE* pWinType ;
HtmlHelp(
GetDesktopWindow(),
\"Help.chm>mainwin\",
HH_GET_WIN_TYPE,
(DWORD) &pWinType) ;

http://msdn2.microsoft.com/en-us/library/ms670087.aspx

We just changed the name of Flare Skin into \"main\" and everything works perfectly now!

[paulblusas]

As you say, set the skin back to 'main' and all is well.

Thanks.

[i-tietz]

Hi there folks,
we have the same problem now. And in our case the programmed change of the help window doesn't happen (no navigation pane on CSH).
BUT:
We cannot rename our skin to "main", because we have more than one skin ... I don't want to rename the respective skin each time I compile a help ...

I suggest: Flare shouldn't assume that the name of the skin is the name of the window - maybe there should be a field on the "Basic" tab called "Name of Window"?
Any other suggestions?

I'll post a bug/enhancement ...

[wclass]

Was this perhaps an imported project? Going from memory here, but we had this problem with RH projects that used the javascript file "ehlpdhtm.js". Window names are hard coded in that file and imported directly into Flare. If you later rename the generated skin this file is never updated. As we no longer needed this file after the migration, we removed all traces of it and the error message went away. It is a bit tricky getting rid of all the script references, but find/replace using regular expressions did the trick.

[i-tietz]

Hi Margaret,
so did we. To delete the file was one of the first things we did after importing the project. And it also happens with new project ...