I'm puzzled why you aren't using the built-in commands:
ApplicationCommands.Undo
, and
ApplicationCommands.Redo
There are several advantages to using these built-in commands:
- Their key bindings are automatically for you set based on locale (Ctrl-Z and Ctrl-Y may not be the default undo/redo keys in all locales)
- They are honored by
TextBox
and RichTextBox
- They cross the WPF <-> WinForms boundary without any problems
- They work with accessibility interfaces
- They are invoked by built-in "undo" keys on keyboards that have them
So if possible you should use the built in ApplicationCommands
by simply registering CommandBindings
for them at the appropriate places in your code.
More information
If you use the built in undo/redo functionality in both WPF and WinForms, it just works. For example, the following creates two RichTextBoxes, one based on WinForms and one on WPF, and both have full undo/redo capabilities:
<UniformGrid Columns="2"
xmlns:winforms=
"clr-namespace:System.Windows.Forms;assembly=System.Windows.Forms">
<WindowsFormsHost >
<winforms:RichTextBox />
</WindowsFormsHost>
<RichTextBox />
</UniformGrid>
Since this works and yours doesn't, try to figure out what is different. You said in your comments you tried removing the custom WPF InputBindings. Have you done the same on the WinForms side? If not, please try it, or if that isn't possible please edit your question to show that code as well.
Note that you can remap ApplicationCommands into your own RoutedCommands: Just add a CommandBinding and in the handler fire your custom RoutedCommand.