Did you click in the shadow of the menu?  That is the main problem.  With the sample code I gave, I am able to reproduce every time.  I can also reproduce it on every machine in my Dev and QA teams. 

Question, did you view the video provided?  This shows the bug.

Scream if you need more from me.  The trick is in the shadow as well as rolling up and down slowly (thereby getting the mouse in the shadow).

Hello,

I did watch the video, but I did not get the behavior I saw in the video.  I will continue to research this.

I just re-verified it is a bug.  I downloaded the Zip, extracted to my desktop, re-"compiled" and ran the Full Demo project.  At first I could not reproduce it but then could every time.

My Infragistics version is 10.3.20103.1000.

Run the Full Demo.

Load a PDF (Document tab, Browse..., Open).  Make sure the PDF has a white background.

Get back to the General tab.

Hit the ultraButton1 button.  See the pretty menu pop up. 

Mouse up and down the menu at least once.

Now click in the Shadow at the bottom of the menu.

Your application is now froze.

This bug is really easy to reproduce if the menu is over something like a PDF. I'll log a bug with one of the test projects that you provided, with slight modifications for an engineer to investigate further. Dave, I'll email you the bug number when I create it in the morning.

An educated guess without debugging much deeper is that the popup menu is not correctly handling an event which in turn causes a thread to wait forever. If you switch to another application and then back to the hung application, the application will be unfrozen (correctly handling that event and closing the popup menu).

Hello DSSavant,

Our engineers have researched this issue and have come up with the following conclusion.

This is an issue in the axWebBrowser control that causes the Form to no longer receive any messages until the form is obscured by some other application.

If you perform a online search, you will find many reports of the axWebBrowser causing a form to become unresponsive. In our case, it is triggered by a mouse-click on a control that allows clicking through to the underlying control. The shadows on our dropdowns are designed to allow the user to click the control on the form under the shadow. This is done by overriding WndProc() for the WM_NCHITTEST(0x84) message, and setting the result to HTTRANSPARENT (-1).

To demonstrate this issue in the axWebBrowser, create a custom panel using the following code; add an instance of the panel to the form on top of the axWebBrowser control, then run the application. Clicking the panel will cause the same hang.

Panel

()

{

.Red;

}

WM_NCHITTEST = 0x84;

HTTRANSPARENT = (-1);

m)

{

.WM_NCHITTEST)

{

.HTTRANSPARENT;

}

else

There is no way for us to determine what the shadows are over, or prevent the hang from occurring. The only solution is to turn off the menu shadows by setting the UltraToolbarsManager's ShowMenuShadows property to False.

Please let me know if you have any other questions about this.

Torrey,

Thanks. This post though did in fact sit for about 10 months before anyone looked at it and said "I can't reproduce it, I need more information". This post is not meant as a slam, more of a frustrated wake-up call.

DSSavant said:

Glad Infragistics found it.

May I ask why it took 10 months for this post to see any action?

I can't speak for everyone, but I started 4.5 here months ago. Having been an Infragistics customer for 5 years before that, I can relate with your frustration. Anytime, I come across a post like this, I take time out to investigate and answer it.

My guess is that Dave wasn't able to replicate the bug because it requires a specific scenario with com interop for triggering.

Glad Infragistics found it.

May I ask why it took 10 months for this post to see any action?