ID Number: Q70358
1.70 1.83 | 1.60 1.70 1.83
MS-DOS | OS/2
buglist1.60 buglist1.70 buglist1.83
Summary:
When using QuickHelp (QH.EXE) with certain help files, a problem
(described below) may occur if there is exactly one blank line below
the text displayed by QuickHelp. In this situation, the help lines can
be shifted down one line (by positioning the mouse on the elevator box
and clicking the left mouse button), which results in the problem.
The problem that occurs when the lines are shifted down depends upon
whether you are running QuickHelp under DOS or OS/2. Under DOS, the
screen will go blank. Scrolling up at this point puts garbage on the
screen.
Under OS/2, the list of topics will shift down one row leaving a blank
line at the top of the screen. The topics brought up by selecting any
line will be the topic listed on the next line down. If you then
select the blank line with the mouse or move off the blank line and
back onto it with the cursor, you will get a protection violation.
More Information:
The OS2.HLP help file that shipped with Presentation Manager Toolkit
for OS/2 version 1.20 can be used to demonstrate this problem. Make
sure OS2.HLP can be accessed from QuickHelp and do the following:
1. Before entering QuickHelp, enter a 50-line display mode.
2. Start QuickHelp.
3. Select Categories and choose OS/2 API.
4. Choose Function group.
5. At this point, the elevator for the scroll bar will appear at the
bottom of the page. Position the cursor on the elevator, just above
the down arrow of the scroll bar, and click the left mouse button.
6. The highlight will be at the top of the screen on a blank line.
Press the UP ARROW key.
Depending on the operating system, one of the previously described
problems will occur.
Other situations where these problems may occur are in 25-line mode on
the "Region functions" screen or the "Window functions." These screens
can be reached by selecting Categories, choosing OS/2 API, and then
sequencing through the screens with the N key until reaching the
appropriate screen.
Microsoft has confirmed this to be a problem in QuickHelp versions
1.60, 170, and 1.83. We are researching this problem and will post new
information here as it becomes available.