I have a couple of related questions:
First, according to the documention, I see that one can use the 'RadWindow.ResponseButton' attached property to associate a button with the 'Enter' or 'Escape' key presses. However, it only mentions that the button's Click event is invoked when the key is pressed. I'm not seeing any mention of the bound 'Button.Command' being executed, which is what is needed in an MVVM scenario. And, indeed, it doesn't seem to work when I try it. Is there some way I can get this to work? If not, are there plans?
Second, I actually already implemented a framework where, in XAML, I can tag any control with the button that is associated with the 'Enter' and 'Escape' keys. This framework relies on handling the 'UIElement.KeyDown' event and it works great for pretty much any kind of FrameworkElement container - Grid, StackPanel, ChildWindow, etc. However, it doesn't work with the RadWindow, apparently because it seems to be suppressing the KeyDown event - at least, it never seems to be getting raised. Do you have any idea why this would be the case and if there is some way to not suppress this event?
Thanks,
Terry Foster
First, according to the documention, I see that one can use the 'RadWindow.ResponseButton' attached property to associate a button with the 'Enter' or 'Escape' key presses. However, it only mentions that the button's Click event is invoked when the key is pressed. I'm not seeing any mention of the bound 'Button.Command' being executed, which is what is needed in an MVVM scenario. And, indeed, it doesn't seem to work when I try it. Is there some way I can get this to work? If not, are there plans?
Second, I actually already implemented a framework where, in XAML, I can tag any control with the button that is associated with the 'Enter' and 'Escape' keys. This framework relies on handling the 'UIElement.KeyDown' event and it works great for pretty much any kind of FrameworkElement container - Grid, StackPanel, ChildWindow, etc. However, it doesn't work with the RadWindow, apparently because it seems to be suppressing the KeyDown event - at least, it never seems to be getting raised. Do you have any idea why this would be the case and if there is some way to not suppress this event?
Thanks,
Terry Foster