We have made zero code changes between win forms 2009.1000 and the hot fix 2009.2012 versions but now on doing this line of code
Parameter name: index at System.Collections.ArrayList.get_Item(Int32 index) at Infragistics.Win.UltraWinTree.NodeClientAreaUIElement.PositionChildElements() at Infragistics.Win.UIElement.VerifyChildElements(ControlUIElementBase controlElement,Boolean recursive) at Infragistics.Win.UIElement.VerifyChildElements(Boolean recursive) at Infragistics.Win.UIElement.VerifyChildElements() at Infragistics.Win.UltraWinTree.UltraTreeUIElement.PositionChildElements() at Infragistics.Win.UIElement.VerifyChildElements(ControlUIElementBase controlElement,Boolean recursive) at Infragistics.Win.UIElement.VerifyChildElements(Boolean recursive) at Infragistics.Win.UIElement.VerifyChildElements() at Infragistics.Win.UltraWinTree.UltraTreeNode.BringIntoViewHelper(Boolean includeChildNodes,Boolean includeHorizontal, Boolean includeVertical, Boolean leftOnly) at Infragistics.Win.UltraWinTree.UltraTreeNode.BringIntoViewHelper(Boolean includeChildNodes, Boolean includeHorizontal) at Infragistics.Win.UltraWinTree.UltraTree.SetActiveNode(UltraTreeNode node, Boolean bringIntoView, Boolean adjustHorizontalPosition) at Infragistics.Win.UltraWinTree.UltraTree.set_ActiveNode(UltraTreeNode value) at Program.Main.ultraTree1_Build(Int32 mode) at Program.Main.Treeview(Int32 type)Thanks :¬)
Hmm, we are getting the same error too. Same circumstances with no code changes between the orignal release and the hotfix.
It seems to happen when we are setting the ActiveNode to something other than nothing (in our case we have just added a new node).
This only is happening if there exists at least one node in the TreeView before attempting to set the ActiveNode.
Forgot to include the call stack:
at System.Collections.ArrayList.get_Item(Int32 index) at Infragistics.Win.UltraWinTree.UltraTreeNode.IsFirstVisibleNodeInIslandHelper(Int32 topNodeVisibleIndex) at Infragistics.Win.UltraWinTree.UltraTreeNode.DisplaysHeaderAreaHelper(Int32 topNodeVisibleIndex) at Infragistics.Win.UltraWinTree.UltraTreeNode.get_DisplaysHeaderArea() at Infragistics.Win.UltraWinTree.NodeClientAreaUIElement.PositionChildElements() at Infragistics.Win.UIElement.VerifyChildElements(ControlUIElementBase controlElement, Boolean recursive) at Infragistics.Win.UIElement.VerifyChildElements(Boolean recursive) at Infragistics.Win.UIElement.VerifyChildElements() at Infragistics.Win.UltraWinTree.UltraTreeUIElement.PositionChildElements() at Infragistics.Win.UIElement.VerifyChildElements(ControlUIElementBase controlElement, Boolean recursive) at Infragistics.Win.UIElement.VerifyChildElements(Boolean recursive) at Infragistics.Win.UIElement.VerifyChildElements() at Infragistics.Win.UltraWinTree.UltraTreeNode.BringIntoViewHelper(Boolean includeChildNodes, Boolean includeHorizontal, Boolean includeVertical, Boolean leftOnly) at Infragistics.Win.UltraWinTree.UltraTreeNode.BringIntoViewHelper(Boolean includeChildNodes, Boolean includeHorizontal) at Infragistics.Win.UltraWinTree.UltraTree.SetActiveNode(UltraTreeNode node, Boolean bringIntoView, Boolean adjustHorizontalPosition) at Infragistics.Win.UltraWinTree.UltraTree.SetActiveNode(UltraTreeNode node, Boolean bringIntoView) at Infragistics.Win.UltraWinTree.UltraTree.SetActiveNode(UltraTreeNode node) at Infragistics.Win.UltraWinTree.UltraTree.set_ActiveNode(UltraTreeNode value)
I was not able to reproduce this problem with the latest build; I tried (1) activating a node that is out of the viewable area on a buttom click and (2) activating a child of a collapsed node, and I didn't get an exception. Since more than one person got this to happen it is obviously not terribly difficult to reproduce, but either I am missing a step or the bug has already been addressed. If you can post a small sample that demonstrates the problem, or provide any details that might help to reproduce, we can take a look.
we are getting the same error too, how can i download build 2029. Thanks.
This issue seems resolved (for us, anyway) as of build 2029. Thanks.
I have the same problem without any BeginUpdate(). However EndUpdate() works as a workaround for me, too. I guess the VisibleNodesManager stuff called from EndUpdate() does what has to be done..
bmcloughlin and dpalau:
I've passed the information on this thread to Developer Support, so that a support case will be logged for each of you. That way, you'll be notified when a service release containing the changes that Brian mentions is published. The workaround Brian mentioned should get you up-and-running again in the meantime.
Thank you for verifying my findings :¬)