The InputBindings are more for providing command responses from UI elements that are not usually used for input, e.g. borders, rectangles, etc. For your case I would recommend creating an attached behavior that will receive the Command and CommandParameter properties and once set, will attach a handler on the Checked/Unchecked events, that will raise the command. The attached application demonstrates what I mean. However, it has one small problem - the CommandParameter binding is updated *after* the command is raised - this is because the IsChecked property is set when the Checked/Unchecked events are raised, which is the moment when the command is executed, but the binding is updated after the event handlers. Of course, for custom scenario like this you could hardcode the command parameter in the CommandCanExecuteChanged and ToggleButtonCheckedUnchecked methods to be always the value of the IsChecked property and everything should work as expected.
All the best,
the Telerik team
Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking
system and vote to affect the priority of the items.