http://ayende.comAyende @ RahienCopyright (C) Ayende Rahien 2004 - 2021 (c) 202660What I do for that is make an update binding on enter behavior and apply it to these sorts of fields. That way you aren't getting bound per key stroke and youg et the new value on enter. http://ayende.com/4636/wpf-default-buttons-and-input#comment9http://ayende.com/4636/wpf-default-buttons-and-input#comment9Sat, 25 Sep 2010 23:07:44 GMTHaving made some critical comments, I must also add that I'm involved in writing a WPF app (Cradiator - [http://cradiator.codeplex.com/](http://cradiator.codeplex.com/) ) that takes advantage of WPF graphical features such that I would have no idea how to write the same app in WinForms. Not only that, but it would likely be so difficult & painful, that I think it would be beyond my ability to convert it to WinForms (or Win32) - I rate WPF highly in this context. Yay for allowing me to write apps with graphical complexity that were previously out of my reach. http://ayende.com/4636/wpf-default-buttons-and-input#comment8http://ayende.com/4636/wpf-default-buttons-and-input#comment8Thu, 23 Sep 2010 01:17:14 GMTAnd, as far as i know, there is a difference between default binding mode in xaml and c#. http://ayende.com/4636/wpf-default-buttons-and-input#comment7http://ayende.com/4636/wpf-default-buttons-and-input#comment7Wed, 22 Sep 2010 11:33:39 GMT@tomasz kubicki: I think you're not really right. http://ayende.com/4636/wpf-default-buttons-and-input#comment6http://ayende.com/4636/wpf-default-buttons-and-input#comment6Wed, 22 Sep 2010 08:55:25 GMTI've made a couple of apps in WPF. The truth is it's simply overengineered. Simple things made in Winforms can be extremly hard in WPF. WPF lacks of predefined good looking consistent styles, and it's internal logic makes it imposible to do an usable gui designer for it (if you think this one from vs2010 is good then..come on. can you make app without hand edited XAML? In forms it was possible) http://ayende.com/4636/wpf-default-buttons-and-input#comment5http://ayende.com/4636/wpf-default-buttons-and-input#comment5Wed, 22 Sep 2010 05:52:24 GMTI sometimes see WPF as a minefield, with issues such as these as the explosives. They each take a few hours to defuse and sometimes you end up having to put your developers back together again - usually it's just their hair, but it can be worse. We have morphine, in the form of coffee, on hand on the battlefield (dev room) at all times. http://ayende.com/4636/wpf-default-buttons-and-input#comment4http://ayende.com/4636/wpf-default-buttons-and-input#comment4Wed, 22 Sep 2010 03:38:28 GMTHey..that bug report looks familar! Thanks for addressing this so quickly :) http://ayende.com/4636/wpf-default-buttons-and-input#comment3http://ayende.com/4636/wpf-default-buttons-and-input#comment3Tue, 21 Sep 2010 13:01:17 GMTI had almost exactly the same problem some days ago, just with the added complexity that I could not use OnPropertyChanged because that does not really work with FormatString bindings: [www.tigraine.at/.../beware-of-button-isdefaultt...](http://www.tigraine.at/2010/09/13/beware-of-button-isdefaulttrue-in-wpfsilverlight/) greetings Daniel http://ayende.com/4636/wpf-default-buttons-and-input#comment2http://ayende.com/4636/wpf-default-buttons-and-input#comment2Tue, 21 Sep 2010 11:44:26 GMTWPF has 2 kinds of focus, Visual one and Keyboard one. These really sucks http://ayende.com/4636/wpf-default-buttons-and-input#comment1http://ayende.com/4636/wpf-default-buttons-and-input#comment1Tue, 21 Sep 2010 10:33:30 GMT