home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 10 Tools
/
10-Tools.zip
/
bugalr.zip
/
BUGALERT.HLP
(
.txt
)
next >
Wrap
OS/2 Help File
|
1993-06-12
|
29KB
|
835 lines
ΓòÉΓòÉΓòÉ 1. Help for BugAlert ΓòÉΓòÉΓòÉ
Use BugAlert to view various pieces of information from windows or
applications.
Related Information:
o Purpose of BugAlert
o Registration of BugAlert
o Modes of BugAlert
o Harvesting information from windows
o BugAlert hotkey
o BugAlert with IPMD debugger
o Defaults
o Known bugs
o Notes
o Future
ΓòÉΓòÉΓòÉ 1.1. Purpose of BugAlert ΓòÉΓòÉΓòÉ
The purpose of BugAlert is to help debug an application. It does this by
harvesting information from windows and applications and can be used in
conjunction with the IPMD debugger providing information that's not currently
available. Used with the IPMD debugger, it can facilitate setting a breakpoint
in a window procedure when given the value of the window handle.
BugAlert consists of four basic windows, i.e., the main dialog window, the mode
dialog window, the information dialog window and the window data dialog window.
The main window consists of the system menu icon, title bar, menu bar and two
checkboxes. The mode dialog window consists of five groups of buttons (radio
buttons and checkboxes) and defines the current mode of BugAlert The
information dialog window consists of three listboxes and several static text
fields and displays the information harvested from either the window or window
handle pointed to by the mouse. The window data window consists of a menu bar
and a multi-line entry field control and displays the extra bytes of memory
associated with a window class.
The system menu in the mode, information and data dialog windows has been
altered so that these windows can not be closed down, they can only be hidden.
The left button double click and ALT+F4 hide the windows instead of closing
them down. BugAlert can only be closed down from the main dialog window. If
the EXIT menu item is used the window positions are saved, whereas, if the left
button double click, ALT+F4 or CLOSE menu items is used, they are not.
The information displayed for all modes is as follows:
Both parent and owner window lineage along with the window handle, id,
title, class, style flags, procedure address, process and thread ids,
rectangle coordinates and class bytes for the currently selected window.
The style flags (class, window and control) are parsed and the mnemonics
listed in the Style: list box.
Another dialog can be brought up that lists all the windows currently on the
desktop along with certain attributes whether they're visible or not.
ΓòÉΓòÉΓòÉ 1.2. Registering BugAlert ΓòÉΓòÉΓòÉ
By sending $35 to:
RDW Controls, 11111 Berwick Drive, Rancho Cucamonga, CA 91730
You will then receive a registered copy of BugAlert.
The unregistered copy of BugAlert always wakes up with the About window and it
stays up until the OK button is click or the Enter key pressed. Also, the
Settings menu and the Actions menu item Enum are disabled.
The registered copy of BugAlert wakes up the first time with the About window
and upon pressing the Register button a dialog comes up to actually register
your copy. Once this is done BugAlert wakes up without the About window.
Also, nothing is disabled.
There are two pieces of information required in the registration dialog--the
name under which BugAlert is to be registered and the serial number that is
supplied on the BugAlert diskette.
ΓòÉΓòÉΓòÉ 1.3. Modes of BugAlert ΓòÉΓòÉΓòÉ
The mode in which BugAlert will operate is defined in the mode dialog. This is
shown by clicking the Show Mode Dialog checkbox in the main BugAlert window.
The mode dialog contains five groups: Level, Source, Breakpoint, Highlight and
File Names.
Level tells BugAlert at what window level to harvest its information, i.e.,
Frame implies the immediate frame window parent of the window currently under
the mouse and Child implies the window immediately under the mouse.
Source tells BugAlert where to harvest its information, i.e., Window implies
the window under the mouse and Handle implies the text in that window if it
evaluates into a valid window handle and if not, the window itself.
Breakpoint tells BugAlert the breakpoint preferences. Set if checked tells
BugAlert to bring up the breakpoint address dialog in IPMD and load the address
of the window procedure associated with the window handle into the address
entry field. This may take a moment or two to appear. Verify if checked tells
BugAlert to let the user exit the breakpoint address dialog and if not checked
BugAlert will exit the dialog as soon as the address is loaded.
Highlight tells BugAlert the way to highlight the window currently under the
cursor. There are four radio buttons representing four kinds of highlighting
which are made up of combinations of outlining and inverting. Outline implies
that a rectangle made up of a dashed line will outline the window. Fill
implies that the area within the window will be inverted. Both implies that
both kinds of highlighting will be used. None implies that no highlighting
will be used. No highlighting is done in Handle mode.
File Names tells BugAlert where to obtain the names of the debugger and
application. Default Application if checked implies that the application file
name is stored in the .ini file and if not checked or the name is not stored in
the .ini file, a dialog window will come up requesting this information when
starting a debugger session. Default Debugger implies that the debugger file
name is stored in the .ini file and if not checked or the name is not stored in
the .ini file, a dialog window will come up requesting this information when
starting a debugger session.
ΓòÉΓòÉΓòÉ 1.4. Harvesting information. ΓòÉΓòÉΓòÉ
There are two ways to harvest information from windows or window handles. One
way is to browse around the desktop, i.e., click the Actions menu item "Browse"
or the browse hotkey, F11. The other way is to simply place the mouse over the
window or window handle and press the load hotkey, F12.
ΓòÉΓòÉΓòÉ 1.5. BugAlert hotkey. ΓòÉΓòÉΓòÉ
F11, F12 and WM_BUTTON1DOWN have been set aside as hotkeys for BugAlert.
WM_BUTTON1DOWN is only effective while browsing. F12 is not effective while
browsing. F11 is effective any time.
F11 toggles between browse and non-browse operation. F12 harvests the
information dialog from the window or window handle (see mode flags) beneath
the cursor. WM_BUTTON1DOWN stops browsing. F12 also sets a breakpoint if the
debugger is operational (see mode flags).
ΓòÉΓòÉΓòÉ 1.6. Bugalert with IPMD debugger ΓòÉΓòÉΓòÉ
The IPMD debugger is started as a child process from BugAlert by clicking the
Actions menu item Debug start. (This same menu item becomes Debug stop after
the debugger comes up.) For BugAlert to work properly with the debugger in
operation, the debugger must be in asynchronous mode.
The debugger then comes up and is operated in the same way as you would without
BugAlert. BugAlert can be in any mode to start a debugger session and the
information harvested is the same as in a normal session. But setting
breakpoints requires a special mode setting.
This special mode includes Child level, Handle source and Set breakpoint. The
level, source and highlight mode are automatically set upon starting a debugger
session. The Set breakpoint is set by the user and if checked, breakpoints can
be set. Once the debugger is operating the mode can be changed, but for a
breakpoint to be set this special mode must be set.
A breakpoint can be set in one of two ways. (1) Place the mouse over the
window containing the address of the window handle and press F12. (2) While
browsing around the desktop, click the left mouse button over the window
containing the address of the window handle.
ΓòÉΓòÉΓòÉ 1.7. Defaults ΓòÉΓòÉΓòÉ
The mode, highlight, some switches, window positions and registration
information are kept in the BUGALERT.INI file. These serve as defaults every
time BugAlert wakes up and are set automatically every time BugAlert closes
down.
ΓòÉΓòÉΓòÉ 1.8. Known bugs ΓòÉΓòÉΓòÉ
There are some known bugs in BugAlert
(1) The "gun" cursor which is active while browsing reverts back to the "arror"
cursor when passing over a disabled button control. It reverts back to the
"gun" cursor when passing over any BugAlert windows.
(2) Information can not be harvested from a "Group box" window while browsing.
It can be harvested if selected in the enumeration of the desktop windows
dialog.
(3) WARNING: BugAlert has problems dealing with IPMD while the storage dialog
is open. If you need to look at storage that's ok, but you must close down
this dialog before using BugAlert operations again.
ΓòÉΓòÉΓòÉ 1.9. Notes ΓòÉΓòÉΓòÉ
(1) If a window is identical in size and on top of another window, BugAlert
will only harvest the information on the bottom window while browsing or with
the browse hotkey. But the information on any window can be harvested by
selecting that window in the enumerated list in the enumeration dialog.
ΓòÉΓòÉΓòÉ 1.10. Future ΓòÉΓòÉΓòÉ
Future releases of BugAlert will be able to harvest window information or
examine storage addresses that are stored in the window static memory, have a
hot key to make BugAlert visible at any time (it may be buried under other
windows) and work with other OS/2 2.x PM debuggers.
ΓòÉΓòÉΓòÉ 2. Help for Application dialog ΓòÉΓòÉΓòÉ
This dialog contains two entry fields. The first one contains the full-path
and file name of the application to be given to the debugger. The OK button
accepts the information and continues on with the debugging session and Cancel
rejects the information and returns to the normal BugAlert operation.
ΓòÉΓòÉΓòÉ 3. Help for Window Data dialog ΓòÉΓòÉΓòÉ
This dialog contains the window "extra bytes" data and presents it in one of
several views, i.e., bytes, longs, shorts and text.
ΓòÉΓòÉΓòÉ 4. Help for Debug dialog ΓòÉΓòÉΓòÉ
This dialog contains two entry fields. The first one contains the full-path
and file name of your debugger. The second one contains any command line
arguments. The OK button accepts and the Cancel button ignores the
information.
ΓòÉΓòÉΓòÉ 5. Help for information dialog. ΓòÉΓòÉΓòÉ
This dialog contains the information harvested from the window or window handle
under the mouse (see discussion on modes). The number of extra window bytes is
presented here and is displayed in the Window Data dialog.
ΓòÉΓòÉΓòÉ 6. Help for information dialog. ΓòÉΓòÉΓòÉ
This dialog contains the information harvested from the window or window handle
under the mouse (see discussion on modes). The number of extra window bytes is
presented here and is displayed in the Window Data dialog.
ΓòÉΓòÉΓòÉ 7. Help for information dialog. ΓòÉΓòÉΓòÉ
This dialog contains the information harvested from the window or window handle
under the mouse (see discussion on modes). The number of extra window bytes is
presented here and is displayed in the Window Data dialog.
ΓòÉΓòÉΓòÉ 8. Help for information dialog. ΓòÉΓòÉΓòÉ
This dialog contains the information harvested from the window or window handle
under the mouse (see discussion on modes). The number of extra window bytes is
presented here and is displayed in the Window Data dialog.
ΓòÉΓòÉΓòÉ 8.1. Help for mode dialog. ΓòÉΓòÉΓòÉ
This dialog defines the mode in which BugAlert will operate. There are five
groupings labeled, Level, Source, Breakpoint, Highlight, and File Names.
The Level group defines at what window level BugAlert harvests the information.
Selecting Frame implies that it will harvest the information from the frame
window which is under the mouse. Selecting Child level implies that it will
harvest the information from the lowest level of window under the mouse within
the frame window, e.g., individual controls.
The Source group defines where BugAlert harvests the information. Selecting
Handle implies that it will try to evaluate all text strings as window handles
and if successful, the information will be harvested from that window. If not
or if Window is selected, the information will be harvested from the window
itself.
The Breakpoint group has to do with the setting of breakpoints in the debugger.
(These are queried when trying to set a breakpoint and if Child and Handle are
not selected, a breakpoint will not be set.) Checking Set will cause the
breakpoint address dialog to appear with the window procedure address loaded.
Checking Verify will require the user to click the "OK" button on this dialog
to verify the breakpoint, whereas, if this item is not checked, BugAlert clicks
the "OK" button and the user is required to do nothing.
The Highlight group has to do with the way BugAlert highlights the windows it
encounters. Selecting Outline will place a dashed rectangle around the
selected window. Selecting Fill will invert the interior of the selected
window. Selecting Both will both outline and invert the selected. Selecting
None will do nothing to the selected window.
The File Names group tells BugAlert where to get the required file names.
Checking these boxes implies that the associated file names have already been
stored in the .ini file. If they are not checked dialogs will come up
requesting the file information. If they are checked and no file information
has been previously stored, dialogs will come up requesting the file
information.
ΓòÉΓòÉΓòÉ 8.2. Help for the Mode dialog. ΓòÉΓòÉΓòÉ
This dialog defines the mode in which BugAlert will operate. There are five
groupings labeled, Level, Source, Breakpoint, Highlight, and File Names.
The Level group defines at what window level BugAlert harvests the information.
Selecting Frame implies that it will harvest the information from the frame
window which is under the mouse. Selecting Child level implies that it will
harvest the information from the lowest level of window under the mouse within
the frame window, e.g., individual controls.
The Source group defines where BugAlert harvests the information. Selecting
Handle implies that it will try to evaluate all text strings as window handles
and if successful, the information will be harvested from that window. If not
or if Window is selected, the information will be harvested from the window
itself.
The Breakpoint group has to do with the setting of breakpoints in the debugger.
(These are queried when trying to set a breakpoint and if Child and Handle are
not selected, a breakpoint will not be set.) Checking Set will cause the
breakpoint address dialog to appear with the window procedure address loaded.
Checking Verify will require the user to click the "OK" button on this dialog
to verify the breakpoint, whereas, if this item is not checked, BugAlert clicks
the "OK" button and the user is required to do nothing.
The Highlight group has to do with the way BugAlert highlights the windows it
encounters. Selecting Outline will place a dashed rectangle around the
selected window. Selecting Fill will invert the interior of the selected
window. Selecting Both will both outline and invert the selected. Selecting
None will do nothing to the selected window.
The File Names group tells BugAlert where to get the required file names.
Checking these boxes implies that the associated file names have already been
stored in the .ini file. If they are not checked dialogs will come up
requesting the file information. If they are checked and no file information
has been previously stored, dialogs will come up requesting the file
information.
ΓòÉΓòÉΓòÉ 8.3. Help for the Mode dialog. ΓòÉΓòÉΓòÉ
This dialog defines the mode in which BugAlert will operate. There are five
groupings labeled, Level, Source, Breakpoint, Highlight, and File Names.
The Level group defines at what window level BugAlert harvests the information.
Selecting Frame implies that it will harvest the information from the frame
window which is under the mouse. Selecting Child level implies that it will
harvest the information from the lowest level of window under the mouse within
the frame window, e.g., individual controls.
The Source group defines where BugAlert harvests the information. Selecting
Handle implies that it will try to evaluate all text strings as window handles
and if successful, the information will be harvested from that window. If not
or if Window is selected, the information will be harvested from the window
itself.
The Breakpoint group has to do with the setting of breakpoints in the debugger.
(These are queried when trying to set a breakpoint and if Child and Handle are
not selected, a breakpoint will not be set.) Checking Set will cause the
breakpoint address dialog to appear with the window procedure address loaded.
Checking Verify will require the user to click the "OK" button on this dialog
to verify the breakpoint, whereas, if this item is not checked, BugAlert clicks
the "OK" button and the user is required to do nothing.
The Highlight group has to do with the way BugAlert highlights the windows it
encounters. Selecting Outline will place a dashed rectangle around the
selected window. Selecting Fill will invert the interior of the selected
window. Selecting Both will both outline and invert the selected. Selecting
None will do nothing to the selected window.
The File Names group tells BugAlert where to get the required file names.
Checking these boxes implies that the associated file names have already been
stored in the .ini file. If they are not checked dialogs will come up
requesting the file information. If they are checked and no file information
has been previously stored, dialogs will come up requesting the file
information.
ΓòÉΓòÉΓòÉ 8.4. Help for the Mode dialog. ΓòÉΓòÉΓòÉ
This dialog defines the mode in which BugAlert will operate. There are five
groupings labeled, Level, Source, Breakpoint, Highlight, and File Names.
The Level group defines at what window level BugAlert harvests the information.
Selecting Frame implies that it will harvest the information from the frame
window which is under the mouse. Selecting Child level implies that it will
harvest the information from the lowest level of window under the mouse within
the frame window, e.g., individual controls.
The Source group defines where BugAlert harvests the information. Selecting
Handle implies that it will try to evaluate all text strings as window handles
and if successful, the information will be harvested from that window. If not
or if Window is selected, the information will be harvested from the window
itself.
The Breakpoint group has to do with the setting of breakpoints in the debugger.
(These are queried when trying to set a breakpoint and if Child and Handle are
not selected, a breakpoint will not be set.) Checking Set will cause the
breakpoint address dialog to appear with the window procedure address loaded.
Checking Verify will require the user to click the "OK" button on this dialog
to verify the breakpoint, whereas, if this item is not checked, BugAlert clicks
the "OK" button and the user is required to do nothing.
The Highlight group has to do with the way BugAlert highlights the windows it
encounters. Selecting Outline will place a dashed rectangle around the
selected window. Selecting Fill will invert the interior of the selected
window. Selecting Both will both outline and invert the selected. Selecting
None will do nothing to the selected window.
The File Names group tells BugAlert where to get the required file names.
Checking these boxes implies that the associated file names have already been
stored in the .ini file. If they are not checked dialogs will come up
requesting the file information. If they are checked and no file information
has been previously stored, dialogs will come up requesting the file
information.
ΓòÉΓòÉΓòÉ 8.5. Help for the Mode dialog. ΓòÉΓòÉΓòÉ
This dialog defines the mode in which BugAlert will operate. There are five
groupings labeled, Level, Source, Breakpoint, Highlight, and File Names.
The Level group defines at what window level BugAlert harvests the information.
Selecting Frame implies that it will harvest the information from the frame
window which is under the mouse. Selecting Child level implies that it will
harvest the information from the lowest level of window under the mouse within
the frame window, e.g., individual controls.
The Source group defines where BugAlert harvests the information. Selecting
Handle implies that it will try to evaluate all text strings as window handles
and if successful, the information will be harvested from that window. If not
or if Window is selected, the information will be harvested from the window
itself.
The Breakpoint group has to do with the setting of breakpoints in the debugger.
(These are queried when trying to set a breakpoint and if Child and Handle are
not selected, a breakpoint will not be set.) Checking Set will cause the
breakpoint address dialog to appear with the window procedure address loaded.
Checking Verify will require the user to click the "OK" button on this dialog
to verify the breakpoint, whereas, if this item is not checked, BugAlert clicks
the "OK" button and the user is required to do nothing.
The Highlight group has to do with the way BugAlert highlights the windows it
encounters. Selecting Outline will place a dashed rectangle around the
selected window. Selecting Fill will invert the interior of the selected
window. Selecting Both will both outline and invert the selected. Selecting
None will do nothing to the selected window.
The File Names group tells BugAlert where to get the required file names.
Checking these boxes implies that the associated file names have already been
stored in the .ini file. If they are not checked dialogs will come up
requesting the file information. If they are checked and no file information
has been previously stored, dialogs will come up requesting the file
information.
ΓòÉΓòÉΓòÉ 8.6. Help for the Mode dialog. ΓòÉΓòÉΓòÉ
This dialog defines the mode in which BugAlert will operate. There are five
groupings labeled, Level, Source, Breakpoint, Highlight, and File Names.
The Level group defines at what window level BugAlert harvests the information.
Selecting Frame implies that it will harvest the information from the frame
window which is under the mouse. Selecting Child level implies that it will
harvest the information from the lowest level of window under the mouse within
the frame window, e.g., individual controls.
The Source group defines where BugAlert harvests the information. Selecting
Handle implies that it will try to evaluate all text strings as window handles
and if successful, the information will be harvested from that window. If not
or if Window is selected, the information will be harvested from the window
itself.
The Breakpoint group has to do with the setting of breakpoints in the debugger.
(These are queried when trying to set a breakpoint and if Child and Handle are
not selected, a breakpoint will not be set.) Checking Set will cause the
breakpoint address dialog to appear with the window procedure address loaded.
Checking Verify will require the user to click the "OK" button on this dialog
to verify the breakpoint, whereas, if this item is not checked, BugAlert clicks
the "OK" button and the user is required to do nothing.
The Highlight group has to do with the way BugAlert highlights the windows it
encounters. Selecting Outline will place a dashed rectangle around the
selected window. Selecting Fill will invert the interior of the selected
window. Selecting Both will both outline and invert the selected. Selecting
None will do nothing to the selected window.
The File Names group tells BugAlert where to get the required file names.
Checking these boxes implies that the associated file names have already been
stored in the .ini file. If they are not checked dialogs will come up
requesting the file information. If they are checked and no file information
has been previously stored, dialogs will come up requesting the file
information.
ΓòÉΓòÉΓòÉ 8.7. Help for the Mode dialog. ΓòÉΓòÉΓòÉ
This dialog defines the mode in which BugAlert will operate. There are five
groupings labeled, Level, Source, Breakpoint, Highlight, and File Names.
The Level group defines at what window level BugAlert harvests the information.
Selecting Frame implies that it will harvest the information from the frame
window which is under the mouse. Selecting Child level implies that it will
harvest the information from the lowest level of window under the mouse within
the frame window, e.g., individual controls.
The Source group defines where BugAlert harvests the information. Selecting
Handle implies that it will try to evaluate all text strings as window handles
and if successful, the information will be harvested from that window. If not
or if Window is selected, the information will be harvested from the window
itself.
The Breakpoint group has to do with the setting of breakpoints in the debugger.
(These are queried when trying to set a breakpoint and if Child and Handle are
not selected, a breakpoint will not be set.) Checking Set will cause the
breakpoint address dialog to appear with the window procedure address loaded.
Checking Verify will require the user to click the "OK" button on this dialog
to verify the breakpoint, whereas, if this item is not checked, BugAlert clicks
the "OK" button and the user is required to do nothing.
The Highlight group has to do with the way BugAlert highlights the windows it
encounters. Selecting Outline will place a dashed rectangle around the
selected window. Selecting Fill will invert the interior of the selected
window. Selecting Both will both outline and invert the selected. Selecting
None will do nothing to the selected window.
The File Names group tells BugAlert where to get the required file names.
Checking these boxes implies that the associated file names have already been
stored in the .ini file. If they are not checked dialogs will come up
requesting the file information. If they are checked and no file information
has been previously stored, dialogs will come up requesting the file
information.
ΓòÉΓòÉΓòÉ 8.8. Help for the Mode dialog. ΓòÉΓòÉΓòÉ
This dialog defines the mode in which BugAlert will operate. There are five
groupings labeled, Level, Source, Breakpoint, Highlight, and File Names.
The Level group defines at what window level BugAlert harvests the information.
Selecting Frame implies that it will harvest the information from the frame
window which is under the mouse. Selecting Child level implies that it will
harvest the information from the lowest level of window under the mouse within
the frame window, e.g., individual controls.
The Source group defines where BugAlert harvests the information. Selecting
Handle implies that it will try to evaluate all text strings as window handles
and if successful, the information will be harvested from that window. If not
or if Window is selected, the information will be harvested from the window
itself.
The Breakpoint group has to do with the setting of breakpoints in the debugger.
(These are queried when trying to set a breakpoint and if Child and Handle are
not selected, a breakpoint will not be set.) Checking Set will cause the
breakpoint address dialog to appear with the window procedure address loaded.
Checking Verify will require the user to click the "OK" button on this dialog
to verify the breakpoint, whereas, if this item is not checked, BugAlert clicks
the "OK" button and the user is required to do nothing.
The Highlight group has to do with the way BugAlert highlights the windows it
encounters. Selecting Outline will place a dashed rectangle around the
selected window. Selecting Fill will invert the interior of the selected
window. Selecting Both will both outline and invert the selected. Selecting
None will do nothing to the selected window.
The File Names group tells BugAlert where to get the required file names.
Checking these boxes implies that the associated file names have already been
stored in the .ini file. If they are not checked dialogs will come up
requesting the file information. If they are checked and no file information
has been previously stored, dialogs will come up requesting the file
information.
ΓòÉΓòÉΓòÉ 8.9. Help for the Mode dialog. ΓòÉΓòÉΓòÉ
This dialog defines the mode in which BugAlert will operate. There are five
groupings labeled, Level, Source, Breakpoint, Highlight, and File Names.
The Level group defines at what window level BugAlert harvests the information.
Selecting Frame implies that it will harvest the information from the frame
window which is under the mouse. Selecting Child level implies that it will
harvest the information from the lowest level of window under the mouse within
the frame window, e.g., individual controls.
The Source group defines where BugAlert harvests the information. Selecting
Handle implies that it will try to evaluate all text strings as window handles
and if successful, the information will be harvested from that window. If not
or if Window is selected, the information will be harvested from the window
itself.
The Breakpoint group has to do with the setting of breakpoints in the debugger.
(These are queried when trying to set a breakpoint and if Child and Handle are
not selected, a breakpoint will not be set.) Checking Set will cause the
breakpoint address dialog to appear with the window procedure address loaded.
Checking Verify will require the user to click the "OK" button on this dialog
to verify the breakpoint, whereas, if this item is not checked, BugAlert clicks
the "OK" button and the user is required to do nothing.
The Highlight group has to do with the way BugAlert highlights the windows it
encounters. Selecting Outline will place a dashed rectangle around the
selected window. Selecting Fill will invert the interior of the selected
window. Selecting Both will both outline and invert the selected. Selecting
None will do nothing to the selected window.
The File Names group tells BugAlert where to get the required file names.
Checking these boxes implies that the associated file names have already been
stored in the .ini file. If they are not checked dialogs will come up
requesting the file information. If they are checked and no file information
has been previously stored, dialogs will come up requesting the file
information.
ΓòÉΓòÉΓòÉ 8.10. Help for the Mode dialog. ΓòÉΓòÉΓòÉ
This dialog defines the mode in which BugAlert will operate. There are five
groupings labeled, Level, Source, Breakpoint, Highlight, and File Names.
The Level group defines at what window level BugAlert harvests the information.
Selecting Frame implies that it will harvest the information from the frame
window which is under the mouse. Selecting Child level implies that it will
harvest the information from the lowest level of window under the mouse within
the frame window, e.g., individual controls.
The Source group defines where BugAlert harvests the information. Selecting
Handle implies that it will try to evaluate all text strings as window handles
and if successful, the information will be harvested from that window. If not
or if Window is selected, the information will be harvested from the window
itself.
The Breakpoint group has to do with the setting of breakpoints in the debugger.
(These are queried when trying to set a breakpoint and if Child and Handle are
not selected, a breakpoint will not be set.) Checking Set will cause the
breakpoint address dialog to appear with the window procedure address loaded.
Checking Verify will require the user to click the "OK" button on this dialog
to verify the breakpoint, whereas, if this item is not checked, BugAlert clicks
the "OK" button and the user is required to do nothing.
The Highlight group has to do with the way BugAlert highlights the windows it
encounters. Selecting Outline will place a dashed rectangle around the
selected window. Selecting Fill will invert the interior of the selected
window. Selecting Both will both outline and invert the selected. Selecting
None will do nothing to the selected window.
The File Names group tells BugAlert where to get the required file names.
Checking these boxes implies that the associated file names have already been
stored in the .ini file. If they are not checked dialogs will come up
requesting the file information. If they are checked and no file information
has been previously stored, dialogs will come up requesting the file
information.
ΓòÉΓòÉΓòÉ 8.11. Help for the Mode dialog. ΓòÉΓòÉΓòÉ
This dialog defines the mode in which BugAlert will operate. There are five
groupings labeled, Level, Source, Breakpoint, Highlight, and File Names.
The Level group defines at what window level BugAlert harvests the information.
Selecting Frame implies that it will harvest the information from the frame
window which is under the mouse. Selecting Child level implies that it will
harvest the information from the lowest level of window under the mouse within
the frame window, e.g., individual controls.
The Source group defines where BugAlert harvests the information. Selecting
Handle implies that it will try to evaluate all text strings as window handles
and if successful, the information will be harvested from that window. If not
or if Window is selected, the information will be harvested from the window
itself.
The Breakpoint group has to do with the setting of breakpoints in the debugger.
(These are queried when trying to set a breakpoint and if Child and Handle are
not selected, a breakpoint will not be set.) Checking Set will cause the
breakpoint address dialog to appear with the window procedure address loaded.
Checking Verify will require the user to click the "OK" button on this dialog
to verify the breakpoint, whereas, if this item is not checked, BugAlert clicks
the "OK" button and the user is required to do nothing.
The Highlight group has to do with the way BugAlert highlights the windows it
encounters. Selecting Outline will place a dashed rectangle around the
selected window. Selecting Fill will invert the interior of the selected
window. Selecting Both will both outline and invert the selected. Selecting
None will do nothing to the selected window.
The File Names group tells BugAlert where to get the required file names.
Checking these boxes implies that the associated file names have already been
stored in the .ini file. If they are not checked dialogs will come up
requesting the file information. If they are checked and no file information
has been previously stored, dialogs will come up requesting the file
information.
ΓòÉΓòÉΓòÉ 8.12. Help for the Mode dialog. ΓòÉΓòÉΓòÉ
This dialog defines the mode in which BugAlert will operate. There are five
groupings labeled, Level, Source, Breakpoint, Highlight, and File Names.
The Level group defines at what window level BugAlert harvests the information.
Selecting Frame implies that it will harvest the information from the frame
window which is under the mouse. Selecting Child level implies that it will
harvest the information from the lowest level of window under the mouse within
the frame window, e.g., individual controls.
The Source group defines where BugAlert harvests the information. Selecting
Handle implies that it will try to evaluate all text strings as window handles
and if successful, the information will be harvested from that window. If not
or if Window is selected, the information will be harvested from the window
itself.
The Breakpoint group has to do with the setting of breakpoints in the debugger.
(These are queried when trying to set a breakpoint and if Child and Handle are
not selected, a breakpoint will not be set.) Checking Set will cause the
breakpoint address dialog to appear with the window procedure address loaded.
Checking Verify will require the user to click the "OK" button on this dialog
to verify the breakpoint, whereas, if this item is not checked, BugAlert clicks
the "OK" button and the user is required to do nothing.
The Highlight group has to do with the way BugAlert highlights the windows it
encounters. Selecting Outline will place a dashed rectangle around the
selected window. Selecting Fill will invert the interior of the selected
window. Selecting Both will both outline and invert the selected. Selecting
None will do nothing to the selected window.
The File Names group tells BugAlert where to get the required file names.
Checking these boxes implies that the associated file names have already been
stored in the .ini file. If they are not checked dialogs will come up
requesting the file information. If they are checked and no file information
has been previously stored, dialogs will come up requesting the file
information.
ΓòÉΓòÉΓòÉ 8.13. Help for the Mode dialog. ΓòÉΓòÉΓòÉ
This dialog defines the mode in which BugAlert will operate. There are five
groupings labeled, Level, Source, Breakpoint, Highlight, and File Names.
The Level group defines at what window level BugAlert harvests the information.
Selecting Frame implies that it will harvest the information from the frame
window which is under the mouse. Selecting Child level implies that it will
harvest the information from the lowest level of window under the mouse within
the frame window, e.g., individual controls.
The Source group defines where BugAlert harvests the information. Selecting
Handle implies that it will try to evaluate all text strings as window handles
and if successful, the information will be harvested from that window. If not
or if Window is selected, the information will be harvested from the window
itself.
The Breakpoint group has to do with the setting of breakpoints in the debugger.
(These are queried when trying to set a breakpoint and if Child and Handle are
not selected, a breakpoint will not be set.) Checking Set will cause the
breakpoint address dialog to appear with the window procedure address loaded.
Checking Verify will require the user to click the "OK" button on this dialog
to verify the breakpoint, whereas, if this item is not checked, BugAlert clicks
the "OK" button and the user is required to do nothing.
The Highlight group has to do with the way BugAlert highlights the windows it
encounters. Selecting Outline will place a dashed rectangle around the
selected window. Selecting Fill will invert the interior of the selected
window. Selecting Both will both outline and invert the selected. Selecting
None will do nothing to the selected window.
The File Names group tells BugAlert where to get the required file names.
Checking these boxes implies that the associated file names have already been
stored in the .ini file. If they are not checked dialogs will come up
requesting the file information. If they are checked and no file information
has been previously stored, dialogs will come up requesting the file
information.
ΓòÉΓòÉΓòÉ 9. Help for registration dialog ΓòÉΓòÉΓòÉ
This dialog contains two entry fields. In the first one enter your name. In
the second enter the product's serial number (BUGyymdd.xx, where "yymdd" refers
to the date upon which your diskette was shipped. "yy" is the last two digits
of the year, "m" is the month number in hex, "dd" is the day of the month. "xx"
is an arbitrary number assigned to the diskette.). This is listed on the
diskette. The OK button accepts and the Cancel button ignores the information.
ΓòÉΓòÉΓòÉ 10. Help for Windows dialog ΓòÉΓòÉΓòÉ
This dialog lists all the windows currently open in the system. If an item in
the list box is selected it is the window whose information is currently shown
in the main dialog. If you select or change the selection the information
about that window will be shown in the main dialog upon closing.
ΓòÉΓòÉΓòÉ 10.1. Help for "Action" menu, item "Browse". ΓòÉΓòÉΓòÉ
This menu item starts BugAlert harvesting information as the mouse moves around
the desktop.
ΓòÉΓòÉΓòÉ 10.2. Help for "Action" menu, item "Debug start(stop)". ΓòÉΓòÉΓòÉ
This menu item starts or stops the debugging process. When debugging this menu
item reads "Debug stop" and when not debugging it reads "Debug start".
ΓòÉΓòÉΓòÉ 10.3. Help for "Action" menu, item "Enum". ΓòÉΓòÉΓòÉ
This menu item brings up another dialog with a listbox that contains all the
windows currently on the desktop whether they're visible or not. This dialog
takes a moment or two to become visible. If a window has already been selected
during the Browse operation it is selected in the list box. If you select
another window in the list box that window is selected and its information
listed when the dialog is closed down.
ΓòÉΓòÉΓòÉ 10.4. Help for "Action" menu, item "Exit". ΓòÉΓòÉΓòÉ
This menu item saves the profile information and then exits BugAlert as opposed
to Alt+F4 which exits without saving the profile information.
ΓòÉΓòÉΓòÉ 10.5. Help for "Settings" menu, item "Application". ΓòÉΓòÉΓòÉ
This menu item sets an application for debugging. The application need not be
set here. It will be set when starting the debugger in the following
conditions:
The application has not been set.
The mode dialog, item Default Application has not been checked.
ΓòÉΓòÉΓòÉ 10.6. Help for "Settings" menu, item "Debug". ΓòÉΓòÉΓòÉ
This menu item sets a debugger to use for debugging an application. The
debugger need not be set here. It will be set when starting the debugger in
the following conditions:
The debugger has not been set.
The mode dialog, item Default Debugger has not been checked.
ΓòÉΓòÉΓòÉ 10.7. Help for "Settings" menu, item "Register". ΓòÉΓòÉΓòÉ
This menu item brings up the registration dialog for the registered copy of
BugAlert.