|
Date: Sat, 10 Feb 1996 15:58:15 UT
From: Stephen Pruitt <[email protected]>
Subject: WinHelp 4.0 Bug list
Here's my current list of bugs that were reported by members of this list and
the CompuServe forum for your info. Please note this is NOT an official list
in any way.
Now that we only have one more maintenance release of the compiler to look
forward to, we need to make sure everything we know of is reported. They'll
only be fixing bugs that affect a significant number of people, not the
extremely rare ones, but there still could be some unreported. If you know of
any that aren't on this list, please write to me with enough details to
reproduce the bug. Let's help Microsoft make this as clean as possible!
Stephen Pruitt
BEYOND HELP - consulting in WinHelp, Multimedia Viewer, and MediaView
Author of "Microsoft Multimedia Viewer How-To"
Section Leader of CompuServe support areas for WinHelp and Windows Multimedia
Business & Finance Category Manager on MS Network
CIS: 70244.365 ** MSNetwork: steve ** Internet: [email protected]
---------------------------------------------------------------------------
WinHelp 4.0 Bugs
As reported by members of the CompuServe WinHelp section and the Internet
WINHLP list.
Transparent bitmaps pick up the background color of the scrolling region, even
if they are located in the non-scrolling region. Reported by Mary Deaton.
WinHelp doesn't use the default indent values used by Word in numbered lists.
You must define a tab stop at 0.25" in Word to get it to display properly in
WinHelp. Note: unlike WinHelp 3.1, you can at least use the same formatting
in all paragraphs. Reported by Stephen Pruitt
The first (or sometimes last) bulleted list will show the wrong sized bullet.
Reported by Stephen Pruitt.
Numbered lists frequently show incorrect numbers (such as 1, 1, 2, 2).
Reported by Stephen Pruitt.
Compiling file afxcore.rtf, provided by VC++, causes hcrtf to GPF after
deleting the line "Record menu" from the first page. Reported by Erik Gawtry.
Help file causes display to flicker madly in 256-color mode. Reported by Ron
Loewy.
An Alink jump to a secondary window in a different HLP file displays a blank
main window as well as the proper secondary window. Reported by Sabrina
Nelson.
You can crash HCW by defining an Include file in the MAP section, then
deleting it without saving the HPJ file in between. A particular sequence of
steps is required. Reported by Lynda G Cone.
Specifying bmct emdash.bmp with compression causes the compiler to crash.
It's OK if compression or the transparency option is removed. Reported by Ann
Adam.
256-color bitmaps print in black and white (no grays) under Win32s 1.30a, Win
3.11, HP LaserJet 4L. Reported by Michael Malcolm Anderson.
Jumps to context IDs or keywords defined in the middle of a topic only work in
non-autosizing windows. Reported by John Hunt.
Jumps to keywords defined in the middle of a topic always display in the
default window defined in the CNT Base statement, not the window designated by
the topic's > footnote. This can cause the above bug also. Reported by John
Hunt.
WinHelp may crash if you select a keyword defined in the beginning of a topic,
then select a keyword defined in the middle of the same topic. Reported by
Kathy Seesing.
You can only copy text from a popup window in a WinHelp 3.1 Help file using
Ctrl+C if the popup is displayed from a secondary window. It fails if
displayed from a main window. Reported by Cub Lea.
A single ampersand in the COPYRIGHT text is replaced by an underscore in
WinHelp 4.0. It was displayed as entered under WinHelp 3.1. The workaround
is to use a double ampersand. Reported by Ann Adam.
If one CNT file is included in another CNT file, WinHelp ignores the default
HLP filename and default window name specifications of the "included" file.
Reported by Stephen Pruitt.
Compiling certain projects with both FTS and compression causes the compiler
to crash. Turning off either compression or FTS allows the compile to
complete. Reported by Lynda G Cone.
Popup hotspots don't work within topics being displayed as context sensitive
help. Reported by Ann Adam.
If a user running in 256-color mode switches focus away from a Help file and
then returns, 256-color WMFs will not have the correct colors. Note: 256-color
BMPs will be redrawn properly. Reported by Ralph Walden.
The external ShellExecute API cannot be used in Help files compiled under
WinHelp 4.0, as it conflicts with the new internal ShellExecute command.
ShellExecute will work properly under WinHelp 4.0 if compiled with the Help
3.1 compiler. Reported by Microsoft.
Internal ShellExecute commands that use the fourth, fifth, or sixth parameters
(operation, path, or topic ID) do not work. Only the first three parameters
can be used. Reported by Microsoft.
If a Help file that uses a normal button bar jumps to a Help file that doesn't
use any buttons, the window is drawn with space left for a button bar. This
extra space is removed after jumping to another topic within the second file.
Reported by Stephen Gilson.
If a page (topic) entry is defined on the same level as a preceding book entry
in a CNT file, the page entry is displayed at the level of the page entries
associated with that book entry. Reported by Kathy Seesing.
The CNT file option :Nofind used to disable the Find tab does not work, and is
rejected by the compiler. Reported by Kathy Seesing.
After replacing the BMP in a SHG file with Shed's Edit Replace option, the
resulting SHG file is twice the size of the original. Reported by Kathy
Seesing.
The scroll bars in WinHelp do not cause the window to be redrawn until the
mouse button is released. Reported by Kathy Seesing.
The KLink macro ignores any keywords after the first, unless the CNT file
includes at least one additional HLP file (even if that file does not exist).
ALink works properly. Reported by Kathy Seesing.
KLink or ALink macros that list multiple keywords will show topics more than
once in the results list if those topics contain hits on more than one
keyword. Each topic appears once for each keyword with a match. Reported by
Kathy Seesing.
If a window is positioned over another window such that a button on the top
window is directly over a button on the lower window, clicking on the visible
button may cause the button in the lower window to be executed. Reported by
Kathy Seesing.
Compare macro doesn't display windows side by side. Reported by Microsoft.
KLink macro executed from a button within a popup window displays the Klink
dialog box behind the popup. It works fine executed from a hotspot. Reported
by Jack Downing.
KLink macro that only matches one topic jumps directly to that topic; it
doesn't display the dialog box as described by the documentation. ALink macro
does display the dialog box properly. Reported by Dave Walker.
A paragraph formatted with "Skip Numbering" in the middle of a numbered list
shows a number 1, and the following paragraph is also numbered 1. Reported by
Graham Hurst.
If two HLP files that use a combined index through the CNT file have some
identical keywords and corresponding topic titles, WinHelp appends the HLP
file name to all but the first duplicated title in the results list. Reported
by Leonor Ciarlone.
Text beginning with or immediately following (not sure which) a typographical
apostrophe in the non-scrolling region is raised or lowered as the font size
is increased or reduced through the WinHelp options menu. Reported by Graham
Hurst.
The HCW Report function cannot open a Help file located in a folder with a
space in the name (such as "Program Files"). Reported by Charles Welty.
HCRTF crashes when compiling an RTF containing an IfThenElse macro containing
macros enclosed in quotes or apostrophes. It compiles and works properly if
the quotes are removed. Reported by John Bradnam.
Items added to the floating menu after it has been displayed do not appear;
they must be added before the menu is displayed. Reported by John Bradnam.
RemoveAccelerator causes erroneous compiler errors with most possible
parameter values, and runtime errors with others. No parameter values were
found that compile and execute properly. Reported by John Bradnam.
A SetPopupColor macro chained after a PopupID macro causes runtime error 1031
A ")" is missing. Reported by William Meisheid.
If a topic that is being displayed as context sensitive help does not exist,
two error message boxes are displayed if Help Author mode is on. Reported by
Steve Rothstein.
Help files containing bullets formatted with Wingding (or other non-Symbol)
fonts and compressed with Hall compression display the wrong bullet character.
Zeck compression does not alter the bullets, and Symbol bullets are not
affected. Reported by Ed Hess.
The ExtInsertItem macro doesn't accept the string versions of the display
state field. Only numeric values will compile successfully. Reported by
Marta Kallstrom.
If a command to create an embedded button contains errors, the command appears
in the displayed text instead of creating a button. The compiler does not
issue any error messages warning of this. Reported by William Meisheid.
ALink and KLink macros that use a default topic must also have a Window
parameter specified. Reported by David VanAusdale.
When a T-CARD instance of WinHelp is started a hidden window is created that
may not be closed when WinHelp is closed. This prevents WinHelp from
reopening. The hidden window can be found with FindWindow("MS_TCARDHELP",0).
Reported by David VanAusdale.
If a user opens another WinHelp window from a T-CARD window, when the second
window is closed a WMCLOSE message is sent to the application to close the
T-CARD window also. Reported by David VanAusdale.
CITATION info is only included when copying topic material; it should also be
included when topics are printed. Reported by Allison Tidd.
If you define an Include file in the Config section, then edit that entry, the
resulting line says "#include #include filename". Reported by Stephen Gilson.
Double underlined text that isn't part of a hotspot appears without
underlining. Reported by David Brown.
Text with dotted underlining appears with a single underline. Reported by
David Brown.
The Escape key can no longer be used with AddAccelerator, even though it's
listed in the usable keycodes. WinHelp now uses Escape to close the window.
Reported by Brett Merkey.
The last line of a topic may be displayed with excess space before it. It
appears to be displayed with the "space before" option of the paragraph.
Reported by Dana Cline.
Autosizing for small secondary windows doesn't always provide enough height to
display the entire topic. Reported by Dana Cline.
The last topic in an RTF file may be displayed with different formatting than
was assigned to it. The workaround is to create a dummy following topic
that's never used. Reported by Dana Cline.
A button in a secondary window that invokes the Exit() macro causes the
buttons to be erased but the window isn't closed. A similar hotspot works
properly. Reported by Stewart Walker.
Commands in the main [Config] section aren't executed before displaying a
topic displayed through the WinHelp API with HELP_CONTEXT. Reported by Ted
Epstein.
Topics displayed with HELP_CONTEXTPOPUP cannot even include jumps to other
topics. Reported by Microsoft.
|