This question is locked. New answers and comments are not allowed.
Hi,
In our project, we use System.Windows.Interactivity.Behavior<T> heavily to attach behaviors to the RadGridView. After we upgraded to Q2 2011, we have had lots of problems with those behaviors.
One major problem is that the GridView will swallow the mouse click (MouseLeftButtonDown) event and not allow us to handle it in the behavior (like button click or drag & drop). Obviously, the mouse click is not handled properly in this release of the RadGridView. Another problem is that we have a textbox in the behavior and the user input is swallowed by the GridView too (key down) too.
Could you please take a look at this problem? We are using all kinds of working around methods to avoid this problem, which are not the approaches we like. And I am sure users that are using Prism and Behavior will face this problem too.
Thanks a lot!
In our project, we use System.Windows.Interactivity.Behavior<T> heavily to attach behaviors to the RadGridView. After we upgraded to Q2 2011, we have had lots of problems with those behaviors.
One major problem is that the GridView will swallow the mouse click (MouseLeftButtonDown) event and not allow us to handle it in the behavior (like button click or drag & drop). Obviously, the mouse click is not handled properly in this release of the RadGridView. Another problem is that we have a textbox in the behavior and the user input is swallowed by the GridView too (key down) too.
Could you please take a look at this problem? We are using all kinds of working around methods to avoid this problem, which are not the approaches we like. And I am sure users that are using Prism and Behavior will face this problem too.
Thanks a lot!