FIX: MouseUp Event Does Not Fire on Contained Objects

ID: Q221701

The information in this article applies to:

Microsoft Visual FoxPro for Windows, version 6.0

SYMPTOMS

The MouseUp event of a container does not fire when you click on a disabled object within the container. However, the MouseUp event does fire when you click elsewhere in the container object.

STATUS

Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article.

This bug was corrected in Visual Studio 6.0 Service Pack 3. For more information about Visual Studio service packs, please see the following articles in the Microsoft Knowledge Base:

Q194022 INFO: Visual Studio 6.0 Service Packs, What, Where, Why

Q194295 HOWTO: Tell That Visual Studio 6.0 Service Packs Are Installed

MORE INFORMATION

This behavior seems to occur when the container's Move and MouseMove events have had code in them and, therefore, appear in the Properties sheet as having a user procedure attached to them.

Steps to Reproduce Behavior

Create a form.

Place a container control on the form and set the following properties and events:

WAIT WINDOW "MouseDown Event" NOWAIT

WAIT WINDOW "MouseUp Event" NOWAIT

Open the container's Move event, add some code, and then delete it. When you return to the Properties sheet, the Move event should have [User Procedure] next to it instead of [Default]. However, it will be empty.

Repeat step 3 on the MouseMove event of the container.

Right-click the container and choose Edit from the short-cut menu. Place a shape or command button object inside the container and set the following properties:

Run the form.

Click on the container (the blue area) and note that both the MouseDown and MouseUp events fire.

Click on the shape (the green area) and note that only the MouseDown event fires.

Additional query words:

Keywords : kbservicepack kbContainer kbCtrl kbOOP kbVFp600 kbVFp600bug kbVS600sp2 kbVS600SP1 kbVS600sp3fix kbGrpFox
Version : WINDOWS:6.0
Platform : WINDOWS
Issue type : kbbug