This is a migrated thread and some comments may be shown as answers.

DataRow e Expression Result

5 Answers 124 Views

ExpressionEditor

This is a migrated thread and some comments may be shown as answers.

5 Answers, 1 is accepted

answered on 11 Dec 2017, 12:24 PM

Hello Marcello,

I will try to address your questions one by one.

1. This behavior is most likely reproduced due to the fact that the UI is not notified. I tested the control with a DataTable.DefaultView instead and the result preview was updated as expected. Note, that when the DefaultView of a DataTable is used, DataRowView is used instead of DataRow. Raising PropertyChanged notifications by it is handled out-of-the-box. Can you please check this out?

2. The result preview is simply displayed as the Text of a TextBlock. Can you please elaborate on the requirement you are aiming at, as I am not completely able to understand it?

3. May I kindly ask you to share some details regarding this requirement as well? Here is the Visual Structure of RadExpressionEditor. Can you please clarify which functions are not appearing on your end?

Regards,
Stefan
Progress Telerik

Want to extend the target reach of your WPF applications, leveraging iOS, Android, and UWP? Try UI for Xamarin, a suite of polished and feature-rich components for the Xamarin framework, which allow you to write beautiful native mobile apps using a single shared C# codebase.

answered on 13 Dec 2017, 08:20 AM

Hi Stefan,

1) Ok, it works.

2) Not a real problem, in realty. I can access expression returned type via ExpressionEditor.Expression.Type and so validate it only for certain return types. I use user expression as conditions in RadGridView.StyleRule and I suppose that a boolean expression is required.

3) Look this image https://docs.telerik.com/devtools/winforms/gridview/expression-editor/expression-editor

I see now only that this image is about winforms version.

In functions three, "Text" function appears, this is not true in Wpf version, why?

Thanks, marc.

answered on 15 Dec 2017, 05:27 PM

Hi Marcello,

Thanks for the clarification.

1. I am happy that the suggestion regarding the DefaultView is working for you.

2. Though I am still not aware of the exact customization you are aiming at, you should be able to use the Type property of the Expression of RadExpressionEditor in conjunction with an IValueConverter, for example. Based on the given type you should be able to apply the needed style.

3. Such functions are not supported by the UI for WPF RadExpressionEditor. Thus, I have logged this as a feature request in our backlog. You can track the relevant item in the Feedback Portal: Text functions support.

In case further assistance is needed, feel free to update me.

Have a nice weekend, Marcello.

Regards,
Stefan
Progress Telerik

answered on 20 Dec 2017, 03:23 PM

Hello Marcello,

The item you referenced is in the top of our backlog and will probably be developed with the next release but has been previously been postponed due to its complexity.

Regarding the newly-added item, please note that our backlog is prioritized by the demand, complexity and various other criteria of the items. Thus, we can rarely commit to a certain time frame for the introduction of a feature. I can say for certain that with the upcoming R1 2018 release approaching, this new item will be addressed no sooner than the end of January 2018 but if the interest in it is high, we will update its priority accordingly.

Lastly, I can assure you that we have not stopped the development of the RadExpressionEditor control and will continue introducing new features and bug fixes based on our clients' demands.

I hope this clarifies your concerns. If you have any further questions or come across any further issues, do not hesitate to contact us again.

Regards,
Dilyan Traykov
Progress Telerik