Article ID: 116182
Article Last Modified on 12/1/2003
APPLIES TO
- Microsoft CodeView 4.0
- Microsoft CodeView 4.01
- Microsoft CodeView 4.1
- Microsoft Visual C++ 1.0 Professional Edition
- Microsoft Visual C++ 1.5 Professional Edition
This article was previously published under Q116182
SYMPTOMS
Calling the ClipCursor() function restricts mouse movement in CodeView for Windows, the Visual C++ integrated debugger, and the application being debugged. The problem also occurs when you use CodeView for Windows in dual- monitor mode.
RESOLUTION
To work around the problem, enter commands using the keyboard when mouse movement is restricted.
STATUS
Microsoft has confirmed this to be a bug in CodeView for Windows and the Visual C++ debugger. We are researching this problem and will post new information in the Microsoft Knowledge Base as soon as it becomes available.
MORE INFORMATION
To reproduce this problem, use the following steps:
- Add the sample code shown below to the MainWndProc() function in the GENERIC sample found in the SAMPLES directory.
- Build the application in debug mode and set a breakpoint on the ClipCursor function.
- Press F5 to run "Generic". Size the Generic window to be a fraction of the total screen size.
- Choose "Help.About Generic".
- Click the "OK" button in the About dialog box to hit the breakpoint.
- Continue debugging using F8, F10, or F5.
The mouse is now restricted to the small area of the screen that you resized in step 3.
Sample Code
long CALLBACK __export MainWndProc(/* ... */)
{
RECT rect; /* add this line */
switch (message)
{
case WM_COMMAND:
if (wParam == IDM_ABOUT)
{
DialogBox(/* ... */);
GetWindowRect(hWnd, &rect); /* add this line */
ClipCursor(&rect); /* add this line */
break;
}
Additional query words: 4.00 4.01 4.10 1.00 1.50 1.50.01
Keywords: kbbug kb16bitonly KB116182
