VC++ README.WRI Part 2-Visual Workbench (1 of 3)

The information in this article applies to:

• The Visual Workbench included with: Microsoft Visual C++ for Windows, version 1.0

SUMMARY

The text below presents information in Part 2 of the README.WRI file distributed with Microsoft Visual C++ version 1.0. Setup installs README.WRI in the MSVC\HELP directory.

MORE INFORMATION

Additional Shortcut Keys

The following shortcut keys were not listed in the shortcut key tables in Chapter 5 of Visual Workbench User's Guide:

   Visual Workbench
   Shortcut Key        Description
   -------------------------------------------------------------------

   CTRL+U              Change selection to uppercase

   CTRL+u              Change selection to lowercase

   TAB                 (With multiple lines selected) Move lines one
                       TAB stop to the right

   SHIFT+TAB           (With multiple lines selected) Move lines one
                       TAB stop to the left

   SHIFT+CTRL+]        Selects block of text to matching brace

Find Matching Braces Accelerator Key

To use the Find Matching Braces Accelerator Key on a non-US keyboard, press the key shown in the following table. This key is usually above and to the left of the ENTER key.

   Keyboard                        Key
   -------------------------------------------------------------------

   Belgian, French                 CTRL+$

   Canadian                        CTRL+<cedilla>

   Czech                           CTRL+)

   Slovenian                       CTRL+<a diaeresis>

   Danish, Swedish, Norwegian,
   Finnish, Swiss                  CTRL+<diaeresis>

   German, Italian, Spanish        CTRL++

   Hungarian                       CTRL+<U acute>

   Latin American, Dutch           CTRL+*

   Polish                          CTRL+'s
                                   (the "'" should be above the "s")

   Portuguese                      CTRL+'

   United Kingdom                  CTRL+]

   Yugoslavian                     CTRL+<eth>

Register Window

   Shortcut Key     Description
   -------------------------------------------------------------------

   TAB              Move to next register
   SHIFT+TAB        Move to previous register
   HOME             Move to the first register of the line
   END              Move to the last register of the line
   CTRL+HOME        Move to the AX register
   CTRL+END         Move to the CARRY flag

Visual Workbench Windows Not Visible Under Certain Circumstances

Minimized Visual Workbench windows may not be visible under certain conditions when they are subsequently restored. This happens if you take all three of the actions listed below:

• Minimize Visual Workbench child windows within the Visual Workbench frame.
• Minimize Visual Workbench.
• Exit Windows with Visual Workbench in the previously noted state.

To avoid this condition, don't close Windows while Visual Workbench is still running and is minimized.

Interrupting the Visual Workbench Debugger

The Visual Workbench debugger, unlike CodeView, allows you to set breakpoints in a source file while the program being debugged is running. This will usually interrupt your program at a defined breakpoint. In cases where you cannot set a breakpoint to halt the program, such as when encountering an infinite loop, you can interrupt your program by pressing CTRL+ALT+SYSREQ. After this type of interrupt, the Visual Workbench debugger gains control.

Note that if you interrupt your program while Windows or other system code is executing, the results can be unpredictable.

Text for Some Check Boxes May Not Be Visible

With some Windows color schemes, the text associated with check boxes that are disabled may not be visible. If this happens, open the Colors dialog in the Control Panel and either change the Disabled Text color to a color besides Light Gray, or set the Button Face to Light Gray.

Using Visual Workbench Debugger and CodeView for Windows

You cannot use the Visual Workbench Debugger and CodeView for Windows at the same time. Starting the Visual Workbench Debugger while CodeView for Windows is running will generate a generic error (Unknown Error in Windows ( -22 )).

Using the Stop Debugging and Restart Commands

Only use the Stop Debugging and Restart commands on the Debug menu when absolutely necessary. This helps to minimize problems that can be encountered when stopping and restarting a debugging session, due to the fact that the application being terminated does not get a chance to free its own resources or memory, or to unload any DLLs it is using.

Opening QuickWatch on a Variable

During a debug session, you can open the QuickWatch dialog box on any variable by typing the variable name in the Find box on the toolbar and pressing SHIFT+F9. The shortcut keys F1 (Help), F11 (Goto Definition) and SHIFT+F11 (Goto Reference) also work on entries in the Find box on the toolbar, regardless of whether a debug session is running.

Debugging while running SPY.EXE

If you use the SPY.EXE program during a debugging session with the Visual Workbench debugger, only give SPY commands while the program being debugged is running. Do not use SPY to select windows to watch, or close SPY when the program being debugged is at a breakpoint. Doing so can cause both SPY and Visual Workbench to crash.

Debugging System-level Hooks

The Visual WorkBench debugger must set task-level hooks on the program being debugged to prevent it being called when stopped. Thus, the debugger can only debug a task-level hook that the program being debugged has installed for itself.

   Example ( debuggee code ):
   SetWindowsHookEx(hookProc, hInstance, GetCurrentTask( )) ;

Debugging MS-DOS Programs

To debug an MS-DOS program using the integrated debugger, first build it as a QuickWin application and debug it using Visual Workbench. When the program is debugged, rebuild it as an MS-DOS application.

Building MS-DOS Overlaid Applications

MS-DOS overlaid applications built within Visual Workbench require a module-definition file (.DEF) in the project list. Unlike Windows-based project types, you will not be warned by Visual Workbench if your MS-DOS overlaid application does not contain the required module-definition file.

   Part two of the README.WRI file is continued in
   README.WRI-Visual Workbench (Number 2)