Hi There,
I am using a tree map to show some hierarchical data, which you can drill down with. I'm getting a strange bug when drilling down to some of my nodes where the error message shows Object not set to a reference...
I had a brief look at the code and it seems to be when the TreemapNodeInfo if trying to find the LastParentNode.
When I am drilling down, I set a flag on my object before I set that object as the ItemSourceRoot, and this seems to contribute to the error. If I don't set this flag then the error doesn't seem to occur.
I have created a simple demo of this behavior which is attached. If you drill down (click) on most of the nodes it is fine, however if the first node you click on is M the error occurs, it also happens sometimes if you drill down on M twice.
Any help on this problem would be greatly appreciated.
I am seeing a similar problem. I have 2 levels of hierarchical data. When zoomed out, I can remove a child (from the second level) and the treemap updates correctly. But if I am zoomed in to a node (zoomed in one level), and I remove a child that is displayed within that zoomed in node, I get "Object reference not set to an instance of an object."
I am using the WPF version of the Tree Map. I just now updated to 11.1.20111.2053 to see if that solves my problem, and unfortunately, it does not.
Please let me know if you are able to reproduce. Thank you.
Hello,
We have shipped out a new service release where your issue is resolved. I'd be glad to find out if you had tested it out and if it had met your requirements.
You can download the Service Releases by logging to our web site and going to My IG \My Keys and Downloads.
Thank you for using Infragistics Components.
Sincerely,
Krasimir
Developer Support Engineer
Infragistics
www.infragistics.com/support
I have created a support ticket for you in order to link the development issue that Nikolay have logged already. Your case number is CAS-68292-QHSBFX.
If you need any further assistance please do not hesitate to ask.
Is there any work around this for the moment?
It seems that this behaviour is a bug in the Treemap control. The flag that you set raises PropertyChanged event - when this event is raised, the Treemap updates its mappings, but at the same time the ItemsSourceRoot has to be changed. I believe that this is causing the null object. I reproduced the issue by commenting the flag and only calling tag.NotifyPropertyChanged(<any Tag property>).
I have submitted a bug about this issue - bug 80872.