Re: HTML Help
- From: "Tom de Neef" <tdeneef@xxxxxxxx>
- Date: Wed, 22 Nov 2006 12:47:50 +0100
"Alexander Halser" <alexander.REMOVETHIS.halser@xxxxxxx> schreef in bericht
news:45638f37$0$2617$91cee783@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
The reason for the stay-on-top mode is the window handle that you use in
the
help call as the first parameter. You could set the handle to 0 to disable
the
stay-on-top. But not so with training card help... this explicitely
requires a
handle to send the WM_TCARD messages to.
A solution would be to create an independent window handle in your
application
that can receive the message but does not have a window. This makes the
help
window independent from your application window or form while your app
still
receives the training card messages.
Yes, it works. But not the way I want it to be.
It has a behaviour like Calling HTMLhelp(0, ... as you predicted, while it
can receive messages.
The nice thing with HTMLhelp(0, is that the help window can be accessed even
though the app has the focus in a modal window. So you can step through a
help training scheme which opens modal windows in the app. Good!
But as soon as you then click in one of the application forms, the help
window disappears behind the app's main window. Because it does not stay on
top.
I want it to work the way Help works in HTML Help Workshop: the help window
is independent in its focus, and stays on top of the application when the
app opens a modal window (eg file-open). In that way you can follow the help
instructions while progressing the steps in the application.
You think that is possible ?
Tom
.
- Follow-Ups:
- Re: HTML Help
- From: Alexander Halser
- Re: HTML Help
- References:
- HTML Help
- From: Tom de Neef
- Re: HTML Help
- From: Alexander Halser
- HTML Help
- Prev by Date: Re: HTML Help
- Next by Date: Forms: modal and stay-on-top
- Previous by thread: Re: HTML Help
- Next by thread: Re: HTML Help
- Index(es):
Relevant Pages
|