I've been working with the yWorks for WPF technology for a few years now and have a chance to compare it to the Telerik WPF Diagramming framework and API sets; in my mind, these are complex and advanced UI frameworks. However, getting started is a long learning curve in many areas of geometry, some trigonometric calculations, systems programming, and some advanced animations work.  We are working to create the following technologies using the Diagramming frameworks:

• OWL 2 DSL Logic and Visualization facilities
• DSL Composition Editor and Visualization facilities
• Microsoft Graph Engine TSL Editor
• Real-time Workflow CMN and DMN Materializer and Interactive Visualization Facilities

I've been using yWorks - a fantastic technology and product, but expensive; it would be great if there was a better set of samples and tutorials around the dynamic use of the Diagramming APIs set for runtime capabilities. I think I've seen what guidance Telerik has made available to date; are there some additional resources available and what type of "professional services" might be available.

Tavi

Hello

Checked that the designer crashes when setting the DataContext viewmodel in xaml.

Please check the attached file for details. Here is a simple example source.

It also sends an associated link about the occurrence of the exception.
My Post
Feedback Post


Additionally, if you attach the DataContext to the xaml, when the designer crashes, clearing the RadGridView's ItemsSource will bring the designer back to display.


Could you solve this problem?
Thanks.