My HTML Help window can't simply be dragged like
ordinary winows can... you have to click on the system
menu and select Move, then drag with the 4-way arrow cursor.
Needless to say, this is an annoyance!
I'm using HTML Help Workshop v4.54. I assumed this was
something to do with the Window line in the HHP file, but
if so I haven't found the magic option yet.
Any help would be greatly appreciated!
Best regards,
Bob Masta
DAQARTA v3.50
Data AcQuisition And Real-Time Analysis
www.daqarta.com
Scope, Spectrum, Spectrogram, FREE Signal Generator
Science with your sound card!
> MyHTML Helpwindow can't simply be dragged like
> ordinary winows can... you have to click on the system
> menu and select Move, then drag with the 4-way arrow cursor.
> Needless to say, this is an annoyance!
It sounds like you've set one or more options on the Styles or
Extended Styles tab of the Window Types dialog box, which you open by
clicking the Add/Modify Window Definitions button on the left toolbar.
If you can paste the contents of your project (.hhp) file into a
reply, I can take a look. I probably only need to see the contents of
the [WINDOWS] section, at least initially.
Does this problem affect other .chm files on your machine, and does
your .chm file misbehave on other machines?
Pete
>Bob,
>
>> MyHTML Helpwindow can't simply be dragged like
>> ordinary winows can... you have to click on =A0the system
>> menu and select Move, then drag with the 4-way arrow cursor.
>> Needless to say, this is an annoyance!
>
>It sounds like you've set one or more options on the Styles or
>Extended Styles tab of the Window Types dialog box, which you open by
>clicking the Add/Modify Window Definitions button on the left toolbar.
>If you can paste the contents of your project (.hhp) file into a
>reply, I can take a look. I probably only need to see the contents of
>the [WINDOWS] section, at least initially.
>
>Does this problem affect other .chm files on your machine, and does
>your .chm file misbehave on other machines?
>
>Pete
Pete, thanks for the offer of help. The problem doesn't affect other
CHMs on this machine, but it does misbehave on other machines.
There is nothing checked in either Styles or Extended Styles under
Add / Modify Window Definitions.
Here is the [WINDOWS] section of the HHP:
[WINDOWS]
Daqarta="DaqartaHelp","Daqarta.hhc","Daqarta.hhk",
"dw_ii00.htm",,,,,,0x63520,, 0x60300e,[271,372,593,566],,,,,,,0
The 0x60300e is to provide Previous and Next buttons; it was
originally 0x300e. I have already tried changing that back to see
if there was some connection, but no difference.
Many thanks!
The window definition line is fine; I've been unable to reproduce the
problem by adding it to a test .hhp file. If you're willing to zip up
and send me your help project, I'll be happy to take a further look.
(I assume that it's roughly the same size as the version that
accompanies your Daqarta v3.50 download.)
You mentioned that you're using HTML Help Workshop v4.54. If this
isn't a typo, you may want to download the 4.74 version from here:
http://msdn2.microsoft.com/en-us/library/ms669985(VS.85).aspx
Pete
Yes, that version number was from memory... it's really v4.74.
Thanks for the offer to look over my Help project. But before I
do that, I think I will try creating a simple dummy Help using all
the defaults from HTML Help Workshop, and if that works OK
I'll look for differences with my real Help.
I was hoping this problem was due to some obvious mistake,
but if it's going to take some effort to find, I feel I should be
doing the bulk of that effort. But I may have more questions in the
near future! <g>
Many thanks,
>On Fri, 1 Feb 2008 06:35:11 -0800 (PST), Pete Lees
><PD....@btinternet.com> wrote:
>
>>Bob,
>>
>>The window definition line is fine; I've been unable to reproduce the
>>problem by adding it to a test .hhp file. If you're willing to zip up
>>and send me your help project, I'll be happy to take a further look.
>>(I assume that it's roughly the same size as the version that
>>accompanies your Daqarta v3.50 download.)
>>
>>You mentioned that you're using HTML Help Workshop v4.54. If this
>>isn't a typo, you may want to download the 4.74 version from here:
>>
>>http://msdn2.microsoft.com/en-us/library/ms669985(VS.85).aspx
>>
>>Pete
>
>Yes, that version number was from memory... it's really v4.74.
>
>Thanks for the offer to look over my Help project. But before I
>do that, I think I will try creating a simple dummy Help using all
>the defaults from HTML Help Workshop, and if that works OK
>I'll look for differences with my real Help.
>
>I was hoping this problem was due to some obvious mistake,
>but if it's going to take some effort to find, I feel I should be
>doing the bulk of that effort. But I may have more questions in the
>near future! <g>
>
>Many thanks,
>
I just realized something: The same CHM file that can't
be moved when invoked by my program, is perfectly normal
when invoked for viewing in HTML Help Workshop. That
indicates to me that the CHM is not the problem, but rather
something about the way my program is invoking it. Time
for some bug hunting!
Best regards,
FOUND IT! The problem was that I was actually trying to
follow the advice in HTML Help Workshop. I was using
HH_INITIALIZE and HH_UNINITIALIZE (along with
HH_PRETRANSLATEMESSAGE so that Help could
see PgUp and PgDn keys) because that was recommended
for multithreaded apps. But in trying to get a clue as to
what I might have done wrong, I stumbled onto some advice on
a game-writing site that stated that these aren't really needed
since most apps are single-threaded. I cut those out, so
that now I just use HH_HELP_CONTEXT and HH_HELP_FINDER
(plus HH_CLOSE_ALL on exit, even though the game site
implied it wasn't needed). BINGO! Everything works as it should:
The Help window can be dragged, and it gets PgUp/PgDn properly.
My app is "multi-threaded", but the other threads are just for sound
card event handling. I suspect that the HHW advice was really meant
for apps that have much more API stuff going on in their other
threads. (Sound card event threads can't make any API calls except
for a chosen few "safe" ones.) This still begs the question of how
such an app would be able to have a draggable Help window, but
I'll burn that bridge when I get there... if ever! <g>
Hope this helps somebody else from making the same mistake...