In your case you should look at the order in which the mouse events fire (the treeview) The treeview is responsable for this and not the RC !!!!

 

If you would hold the left button down (second click of double click) and drag the mouse outside the picturebox you don't get a mouseUp event !!! and if you release it when mouse is in picturebox area you will get MouseUp event as it should

 

Now, if your treeview reacts on the mouse click or MouseUp event you can't blame the RC for this ?!?!?

 

 

 

And yes, I use still a workaround nearly like yours.

 

I don't know why you need this...

 

Does you underlying control use the MouseUp event? If so I would set a flag in the MouseDown event in order to have a proper click event. The user has to click first before you will handle the MouseUp event.

 

Something like this:

 

Private Sub Form_MouseDown(Button As Integer, Shift As Integer, X As Single, Y As Single)
    flagMouseDown = True
End Sub

Private Sub Form_MouseUp(Button As Integer, Shift As Integer, X As Single, Y As Single)
    If flagMouseDown = True Then MsgBox "Form_MouseUp event"
    flagMouseDown = False
End Sub

 

 

 

 

The same thing, when form unloads, mouse up event of underlying control will be fired. 

 

See Image again @Jebo

 

 

Try this:

set StartUpPosition of form2 to CenterScreen and add Form_MouseUp event in Form1, you will see that the form1_MouseUp event will be fired.

 

 

I think you have to call Bill Gates to have this fixed

 

 

 

DON'T BE SO HASTY!!!

 

THIS IS ONLY A EXAMPLE 4 a better UNDERSTANDING !

In the original-code it is a POPUP-CONTROL (see on command-caption-text: "a popup-simulator")

 

Again: Use the second command-button and you'll see!!!

 

 

It isn't ????

 

 

Option Explicit

Private Sub cmdGo_Click()
Picture1.Enabled = True         ' now allow a MouseUp-Event on this picturebox (!) -> this is ONLY for a better understandig of this sample (!!!)
ReportControl1.Visible = True
End Sub

Private Sub Command1_Click()
Picture1.Enabled = True         ' now allow a MouseUp-Event on this picturebox (!) -> this is ONLY for a better understandig of this sample (!!!)
Form2.Show vbModal
End Sub

Private Sub Command2_Click()
Unload Me
End Sub

Private Sub Form_Load()
Dim i As Integer
Me.Move 3000, 3000

With ReportControl1
    .Columns.Add 1, "A", 300, False
    .Columns.Add 2, "B", 9000, False

    For i = 1 To 5
        With .Records.Add
            .AddItem i: .AddItem "Please DblClick on any row!"
        End With
    Next
    .Populate
End With
End Sub

Private Sub Picture1_MouseUp(Button As Integer, Shift As Integer, X As Single, Y As Single)
MsgBox "Why do U see me???" & vbCr & vbCr & "I'm NOT a event from ReportControl!!!" & vbCr & vbCr & "I'm a MouseUp-Event of another control!", vbExclamation, "What's wrong?"
Picture1.Enabled = False    ' this is ONLY for a better understandig of this sample (!!!)
End Sub

 

Private Sub ReportControl1_RowDblClick(ByVal Row As XtremeReportControl.IReportRow, ByVal Item As XtremeReportControl.IReportRecordItem)
ReportControl1.Visible = False
End Sub

 

 

And what do you mean with second click???

There is NO second click!

And there is NO RC.Visible = True (use the second sample-button: this is a Form.Show vbModal)

 

Please check the sample correctly and test it with another ListControl (like visual basic ListBox!). With a ListBox (OR ANY OTHER CONTROL with a DblClick-Event) this problem don't occurs! ;-)

 

 

I think your "unpleasantly bug" is not one of CJ's concern. If you look at the image it workes as supposed to

 

 

                    |                                       |

                    |       Double click cycle     |

 

 

there is a unpleasantly bug in the ReportControl!

 

If I do a DoubleClick on a row, a MouseUp-Event will give to a control "under" the ReportControl!!!

 

Please see the attachment for more details and a better understanding!