5 Answers, 1 is accepted
0
Hello Steve,
Thank you for noticing this issue. We will investigate it and will provide further information whether this is a TreeView specific issue or an issue in the Application logic of the Class Diagram example.
We updated your telerik account points as a thanks for your cooperation.
Regards,
Petar Mladenov
Telerik
Thank you for noticing this issue. We will investigate it and will provide further information whether this is a TreeView specific issue or an issue in the Application logic of the Class Diagram example.
We updated your telerik account points as a thanks for your cooperation.
Regards,
Petar Mladenov
Telerik
TRY TELERIK'S NEWEST PRODUCT - EQATEC APPLICATION ANALYTICS for WPF.
Learn what features your users use (or don't use) in your application. Know your audience. Target it better. Develop wisely.
Sign up for Free application insights >>
Learn what features your users use (or don't use) in your application. Know your audience. Target it better. Develop wisely.
Sign up for Free application insights >>
0
Steve
Top achievements
Rank 1
Rank 1
answered on 19 Nov 2013, 12:26 PM
Hello Petar, Thanks for your reply, Is this bug in the TreeView will be fixed?
0
Accepted
Hi Steve,
This issue is previously logged in our system under the name:
TreeView: The DefaultImageSource and ExpandedImageSource properties don't work in virtualized tree
If you don not need virtualization (your tree is small and you don't need performance optimization) you can turn it OFF (IsVirtualizing = False) and this will work properly. On the other hand, there is an elegant workaround in MVVM scenarios - do not use these image properties and add Image in the ItemTemplate of the RadTreeView. Then bind its Source to the IsExpanded property and use converter to selected different image sources based on the value of the IsExpanded property.
We think this issue has little priority due to the workaround possible. Furthermore we have to admit that exposing such image properties in our RadTreeView is a mistake in our design. The usual way for such customizations should be ViewModels + ItemTemplates as suggested above.
Regards,
Petar Mladenov
Telerik
This issue is previously logged in our system under the name:
TreeView: The DefaultImageSource and ExpandedImageSource properties don't work in virtualized tree
If you don not need virtualization (your tree is small and you don't need performance optimization) you can turn it OFF (IsVirtualizing = False) and this will work properly. On the other hand, there is an elegant workaround in MVVM scenarios - do not use these image properties and add Image in the ItemTemplate of the RadTreeView. Then bind its Source to the IsExpanded property and use converter to selected different image sources based on the value of the IsExpanded property.
We think this issue has little priority due to the workaround possible. Furthermore we have to admit that exposing such image properties in our RadTreeView is a mistake in our design. The usual way for such customizations should be ViewModels + ItemTemplates as suggested above.
Regards,
Petar Mladenov
Telerik
TRY TELERIK'S NEWEST PRODUCT - EQATEC APPLICATION ANALYTICS for WPF.
Learn what features your users use (or don't use) in your application. Know your audience. Target it better. Develop wisely.
Sign up for Free application insights >>
Learn what features your users use (or don't use) in your application. Know your audience. Target it better. Develop wisely.
Sign up for Free application insights >>
0
Steve
Top achievements
Rank 1
Rank 1
answered on 23 Nov 2013, 08:25 AM
Hello Petar, Thank you for your thorough explanation,
My tree is very large and need performance optimization, I'll wait until the problem is solved.
My tree is very large and need performance optimization, I'll wait until the problem is solved.
0
Hello Steve,
Just to clarify once again. Performance is optimized in the RadTreeView when the Virtualization is turned ON. But it is perfectly suitable for you to workaround this bug with ItemTemplates with Image and ViewModels containing the SourceUri for the Images. This will work with Virtualization turned ON.
Regards,
Petar Mladenov
Telerik
Just to clarify once again. Performance is optimized in the RadTreeView when the Virtualization is turned ON. But it is perfectly suitable for you to workaround this bug with ItemTemplates with Image and ViewModels containing the SourceUri for the Images. This will work with Virtualization turned ON.
Regards,
Petar Mladenov
Telerik
TRY TELERIK'S NEWEST PRODUCT - EQATEC APPLICATION ANALYTICS for WPF.
Learn what features your users use (or don't use) in your application. Know your audience. Target it better. Develop wisely.
Sign up for Free application insights >>
Learn what features your users use (or don't use) in your application. Know your audience. Target it better. Develop wisely.
Sign up for Free application insights >>