Navigation buttons disabled with AutoCommit=false and custom DataTemplates defined
Posted on:30 Apr 2015 10:39
Note: In WPF/Silverlight there is no good approach to tracking, which model properties are bound to the controls in some DataTemplate. On the other hand, AutoCommit=False requires tracking changes in property values to identify whether there are uncommitted changes. Apparently this mechanism cannot easily track, which are the UI-represented properties, it tracks for changes in all of the bound type's properties. Thus RadDataForm could be led to a "blocked" state, if some of the not-bound properties changes its value, while an edit operation is in progress. Using AutoCommit=False with manually-generated property definitions is not recommended, unless the mentioned risk is taken into account.