Gord Dibben was thinking very hard :
GS
What I see in 2003 is Alt + F4 does not close the help window even
when undocked.
It is movable when undocked but remains "attached" to the application
which closes when Alt + F4 is activated.
2007 help window opens in its own distinct window and Alt + F4 will
close it.
I guess 2010 is same as 2007
I get the same behavior. It doesn't matter if the TaskPane is 'docked'
or not because it will always be a 'child' of the MS Office host app.
IOW, it's not a 'normal' window. You can tell this by the missing
sizing buttons in the TitleBar. Note also that TaskPane is listed under
View>Toolbars, which further suggests it's a member of the Toolbars
collection and as such, do not qualify as independant windows (as would
a dialog, for example), and for all appearances behaves much the same
as any undocked toolbar.
This is not the same as the 'dockable' windows in the VBE, which do
have the sizing buttons. However, they do not have independant keyboard
shortcuts that hide them (display only is provided for some not all).
I have a VB6 app that implements display of 2 different 'panes' in much
the same fashion, but use the same keyboard key as the toggle. The
difference here is none because Ctrl+F1 is also the toggle for the
TaskPane regardless of whether a user hit F1 or not. So the action to
be taken is to toggle the display of the control that displays help,
which in this case 'appears' confusing due to the association to "F1".
Just to further clarify Stan's point.., help files usually open in
their stand-alone app window as an "in-process" extension of the host
app. Code mechanisms are in place to ensure that help is controlled by
the host app for its runtime life, meaning when the host app closes so
does any respective help files it opened during runtime. Usually, the
host app stores a ref to the help window's handle so it doesn't open
multiple instances of it when it happens to be covered by foreground
windows or minimized to the tray. The VB6 app I mentioned earlier uses
a stand-alone EXE (an ebook, actually) for its Userguide and so the
mechanism to make it behave like a normal in-process CHM/HLP had to be
included in it's handler routines. Otherwise, it can be used
stand-alone same as a CHM/HLP file can be used outside the host app. I
also use this method of displaying UserGuides in some of my
application-level Excel addins.
--
Garry
Free usenet access at
http://www.eternal-september.org
ClassicVB Users Regroup!
comp.lang.basic.visual.misc
microsoft.public.vb.general.discussion