The documentation for Infragistics 8.1 says Regardless of SelectionType, no two nodes under different parents may ever be selected simultaneously. But nodes under different parents can be selected on pressing the Ctrl key while selection. This dint happen in previous versions. Is there any way to avoid this.
http://help.infragistics.com/Help/NetAdvantage/NET/2008.1/CLR2.0/html/Win_You_Can_Now_Select_Nodes_from_Different_Levels_in_WinTree.html
In previous releases, WinTree is a Windows Forms control that allows for navigation and structure in any Windows Forms application or project. Toolbox Item: UltraTree Namespace: Infragistics.Win.UltraWinTree',event)" class="hsglossaryreference" title="Click to show a definition of this term">WinTree™ only allowed you to select nodes from the same tree level simultaneously. This release, we've broken the level barrier, allowing you to select as many nodes, in as many levels of the tree as necessary. You don't need to perform any extra work in order to turn this functionality on, it just works. However, if you want to manipulate the SelectedNodes collection based on nodes in different levels, you'll need to sort through the collection and identify which Node belongs to which Level.
In previous releases,
WinTree is a Windows Forms control that allows for navigation and structure in any Windows Forms application or project.
Toolbox Item: UltraTree
Namespace: Infragistics.Win.UltraWinTree
A couple of NetAdvantage releases ago, I've made a feature request to publish normal release notes (bugs fixed (independently whether they were found by the customers or internally), features implemented, performance improvements etc.). See http://www.nunit.org/index.php?p=releaseNotes&r=2.4.6
As you can see, nothing was changed. We get the same 3-4 lines of marketing bla-bla-bla.
But the same isnt reproducible when Shift key is pressed while selecting. Only for Ctrl key it allows selection of nodes at any level.
This problem has recently been addressed; you should log an incident so that you are notified when the fix becomes available (it actually might already be). Also note that another effective workaround is to set the SelectionType property on the control-level Override (UltraTree.Override), as opposed to the root nodes collection-level Override (UltraTree.Nodes.Override).
We have also had exactly the same problem with the "new" SelectionBehavior. We did not set it to ExtendedAcrossCollections and even setting it explicitly to UseOverride did not help to fix this selection bug.
Fortunatly we are using our own Drag & Drop Implementation and found a workaround by setting the Tree's SelectionType from SelectType.ExtendedAutoDrag to SelectType.Extended.
(...but we are still looking forward to a BugFix/HotFix)
As I said... if you have an existing application and you did not explicitly turn this feature on (via the SelectionBehavior property) and you are suddenly able to select nodes across parents, then that is a bug and you should report it to Infragistics. Submit an incident to Infragistics Developer Support
How do you turn on that feature? I have just set SelectionType as ExtendedAutoDrag (which I used for previous versions also) and havent used SelectionBehavior property. In spite of this I am able to select multiple nodes at different levels only when I use Ctrl and not when Shift key is pressed. I need to make it revert back to the way it worked in the previous versions.
In v8.1, a new feature was added to allow selection across parent nodes. But this feature is not on by default, you have to explicitly turn it on by setting properties (like SelectionBehavior). So if you have an existing application and you did not explicitly turn this feature on and you are suddenly able to select nodes across parents, then that is a bug and you should report it to Infragistics. Submit an incident to Infragistics Developer Support