Still no reply on this question?  I am having the same difficulty.  How do you wrap the Node text using UltraWebTree?  It is a basic property in the underlying .Net tree control.

Any advice for why I can't seem to find this property?

Thanks in advance,

Dan

I'm having the same problem. Couldn't you guys from Infragistics at least offer an answer to this question? I have spent too much time already trying to find a solution to this problem. Any help is appreciated.

Hi I am using Infragistics treeview control, i need to wrap the text of a node where the text length is more than 20 character, but i am not able to find any property or method which does support my job, I would request you all infra-champs to give a solution, Thanks a lot in advance.

Arindam 

 I've solved this issue in two steps. One is needed for IE 6, and the other for Firefox.

 Step 1.

Assign Node Text using method:

private void SetNodeText(Node n, string text)
        {
            string[ parts = text.Split(new char[ { ' ' });
            StringBuilder sb = new StringBuilder();
            foreach (var p in parts)
            {
                sb.Append(Server.HtmlEncode(p)); sb.Append(" <wbr>");
            }
            n.Text = sb.ToString();
        }

Step 2.

 Call it when creating new nodes AND on NodeSelectionChange - for every node. I needed to update every node on selection change, because otherwise it lost this style in Firefox. In IE it was OK.

        private void SetNodeStyle(Node node)
        {

            //// YOUR STYLE GOES HERE AND....

           node.Style.CustomRules = "white-space: -moz-pre-wrap;";
        }
 

The problem is caused by tag <nobr> used when rendering UltraWebTree.

Wow, that's awesome - much appreciated. I personally thought that wrapping was not possible even with additional css/javascript coding. Thanks a lot for sharing this will certainly be appreciated by a lot of people.

 Interesting approach, but I noticed that it wrapped the second line of text all the way to the left margin again, not taking into account any indentation for levels > 1.  This is not optimal for our use.  But it was good to see someone out there address the issue since IG doesn't seem to be able to do so.

Dan