This is more precise and understandable to me to say that a ‘Delay’ property has been added to the Binding markup extension !This post is a part of the serie on WPF 4.5 new features.The use of Group Name was an issue for me when multiple copies of the same view where shown within a docking window..the radiobuttons from different view instances were interfering with each other..this is not an issue when using a different parent for each radiobutton as a means of seperating them into different groups... I followed the instructions exactly, but my databound value is not being updated when the radio buttons are clicked.Here is an example of a binding which sets a delay of 500 milliseconds: The master/detail scenarii are the one where it can be the most useful for me so I have create a demo project to reproduce it.Let’s say that we a have a list of person and the selected one’s details are displayed.
I believe one issue with having to use multiple group names is that the tabbing behavior does not operate correctly.
It would have been better for lame user to understand if it had the solution/source code file with this in zip. to all the people saying "if people don't understand, too bad, figure it out yourself" This is a TUTORIAL. If it doesn't fulfill it's purpose, whats the point? Effectively the built-in radiobutton functionality is not used at all really (the radiobuttons are all in their own group and the mutual exclusivity is an effect of the binding).
If you're so smart, why are you looking up tutorials? In the end I varied from the example a bit in that I found it safer to isolate each Radio Button from the others by putting each within its own parent (ie each in its own Stack Panel) and not setting a Group Name at all.
It the list of options gets longer, you should prefer a combo or list box instead.
It would have been better for lame user to understand if it had the solution/source code file with this in zip. They are reading this and they dont know what data binding is.