Hello,

Thank you for your post. I have been looking into your question and what I can suggest is creating a style for the XamDataTreeNodeControl and add a Trigger that checks whether the node is active and sets the FontWeight property. Also, you can create a DataTempalte with a TextBlock for the ItemTempalte of the NodeLayout and use the same approach there (add a Trigger and set the FontWeight of the TextBlock). I have created sample application for you that shows how you can implement both of the approaches.

Regarding the approach that you have described, using the ActiveNodeChanged event, using it might cause some issues related to the virtualization of the XamDataTree’s node controls. Since the node controls are virtualized, if you click on the first node to activate it and bold it, and the scroll so the first node is not in view, the node control of the first node will be used for some of the nodes that are coming into view and they will appear bold, even if they are not selected, which is the reason for suggesting to use bindings. When you use styles or templates and use triggers that are bound to a property of an object that is not virtualized, you will avoid such issues and when the same node control is used for different node, the data context of the node control will change and this will re-trigger the setter and you will have the correct appearance. I have created a video that show the issue that will appear when setting the XamDataTreeNodeControl properties in code.

Hello,

I am just checking if you require any further assistance on the matter.

Sincerely,

Krasimir, MCPD

Developer Support Supervisor - XAML

Infragistics