Comments on: Redoing the Options Dialog in BabySmash

By: John Rennemeyer

John Rennemeyer — Wed, 13 Aug 2008 20:10:35 +0000

For the property not getting changed until you lose focus, you should be able to add the following:

UpdateSourceTrigger=PropertyChanged

so you should have:

I haven’t tested this in your sample, but I am using this method when I’m binding a TextBox to a CLR object property and it works great.

I hope this helps.

John
MuvEnum

By: Scott Hanselman's Computer Zen - Learning WPF with BabySmash - Customer Feedback and a WPF Font ComboBox

Fri, 18 Jul 2008 06:13:15 +0000

[...] Settings for this project. Remember that I refactored the Options Dialog a few weeks back using Jason Kemp’s code. This made it easy to just add one additional ComboBox. I’m getting good enough that I added the [...]

By: Jason Kemp

Jason Kemp — Wed, 16 Jul 2008 01:14:09 +0000

@Joe: Yes, you’re right. That is something I neglected to mention.

By: Joe

Joe — Tue, 15 Jul 2008 23:45:33 +0000

Thanks for the great explanation but what happens when a user modifies one of these databound entries and then selects the Cancel button in the dialog?

Wouldn’t the programmer also need to do a Properties.Settings.Default.Reload(); in the OnCancel handler?

By: Jason Kemp

Jason Kemp — Wed, 11 Jun 2008 00:15:49 +0000

@Darrell: My rant wasn’t against Blend; it was against Visual Studio 2008. My feeling is that even if there were a developer and designer collaboration, the developer would be responsible for hooking up data bindings.

But why can’t he do it from the visual designer?

I wasn’t disparaging the collaboration, either. I think that’s great that designers are getting tools that let them design something we can use right in the app; my observation is that it’s rare to have a designer nearby. In my experience, which may be limited, or in the minority, the developers responsible for how the app looks as well as how it works.

By: Darrell

Darrell — Tue, 10 Jun 2008 20:26:01 +0000

Your rant on Blend is off-base. They have vastly improved Blend recently and databinding is fully supported (has been for a while). It very much supports designer-developer interaction allowing on my current project and the past 2 before it to have a designer with limited C# knowledge to be very productive and produce a much more kick-ass GUI than anything a developer would produce. I’m not knocking you as a GUI guy, but my guess is a designer would do better.

That said there are still some glitches in Blend. Specifically adding a new file does not get the file checked into TFS properly. Sigh.

By: Using Commands in BabySmash | a geek trapped in a cool guy’s body

Using Commands in BabySmash | a geek trapped in a cool guy’s body — Wed, 04 Jun 2008 15:32:31 +0000

[...] Related Posts StaticResource does not mean staticRedoing the Options Dialog in BabySmash [...]

By: Improving the Improvements - Cleaning up and adding validation to Baby Smash! Options

Tue, 03 Jun 2008 18:14:25 +0000

[...] Jason Kemp made some excellent improvements to the Baby Smash! Options dialog as part of a community project Scott Hanselman is undertaking in order to improve his and readers WPF skills. [...]

By: StaticResource does not mean static | a geek trapped in a cool guy’s body

Tue, 03 Jun 2008 16:15:28 +0000

[...] My post about BabySmash got hanselmanned. There are some questions in the comments on that post that are worth addressing in another couple posts, so here’s the first. For background, we have Scott’s follow up post, describing how he changed the code because of my post. [...]

By: Kevin Berridge

Kevin Berridge — Tue, 03 Jun 2008 15:13:31 +0000

Wow, that is so bloody simple… I should have seen it coming.

I assume if you had 2 containers on the window that needed to have 2 different DataContexts (if you were passing in more than one data class) that you’d just set the DataContext directly on those containers.

Thanks so much!