We upgraded from 10.3.20103.2015 (Framework 2.0) to 11.2.20112.2019 (Framework 3.5)

But I have also tested with SR 2034. This fails. 10.3 works.

Note that this is now open as case # CAS-85397-BG6V5W

Mike

Hi Mike,

The reason I asked is because I took a look at the Tooltip class and the last change to that class was made in June of 2010. So if the problem you are experiencing occurs in 10.3.20103.2034 but does not happen in 10.3.20103.2015, then it seemed likely that the change in June is what's causing it.

The change that was made was a bug fix that specifically had to do with tooltips that showed formatted text and a tooltip that was being displayed on a dropdown window. So I don't see any way that this change could cause the issue you are experiencing now.

The change prior to that was so long ago, I don't even have a record of it, so it was probably back in like 2007.

It is, of course, possible that the change which caused this exception was in some other class, but without some more information about where to look it's impossible to track it down that way.

So I'm afraid we are back at square one.

Without being able to see the exception occurring, there's very little we can do about something like this. You seem to be able to duplicate the problem when you want to - at least well enough to tell that it happens in one version and not another. Is there no way you can provide us with a sample project and instructions we can follow in order to duplicate the exception? 

I guess I wasn't clear.

The SR 2034 version I was refering to is the LATEST fix - 11.2.20112.2034 - not a 10.3 fix.

When I opend the case I was asked to verify the problem with this latest version.
10.3.20103.2015 works, but all of the 11.2 versions I have tried fail. (I have not tried 11.1) 

So it has to be something that changed after 10.3.20103.2015.

I'll see if I can replicate it in a test app.

Also note that it seems that only the UI DISPLAY is destroyed. Even when it is displaying the red X I can move the mouse over it and [if I make it narrow] I can read the node text by looking at the tooltips that it still displays. If I click on a node [or its tooltip really] then it correctly displays the associated data in the associated textbox. So the underlying functionality of the control is still working - you just can't see the content of the control.

Knowing that, is there maybe a way to 'restore' the visual part of the control?
I could use that as a workaround until it is fixed.

Thanks
Mike

I uploaded a small demo app the recreates the problem and attached it to the Case.

Mike,

I don't see the demo app that you uploaded.  Could you try again?

I uploaded it to case # CAS-85397-BG6V5W

I have attached it here also.

Ok. Thanks to Mike who opened a case (I hadn't that time yet..). And thanks to Infragistics staff that worked to find a solution. We're waiting for service release, then. Bye!

Hi,

Just wanted to let you know I confirmed that this is indeed a bug. It should be fixed in the April service release.

The bug happens when you show a tooltip in one DisplayStyle (like the default style), then try to show a tooltip on the same tree using the WindowsVista DisplayStyle. So it will only happen if you switch styles at run-time after showing a tooltip in the tree at least once.

OK, I see this issue has already been submitted to development.