>Are you saying your son is a programmer and writting a game?

Yep he works for a well established company the develops MMORPGs (not the one that jumps to mind when you say that.) This is his dream job, he's wanted to do since he was about 12 and he's done it, got a nice promotion last week too! Dad couldn't be prouder.<bg>

What language?

C (He also knows C++, VFP and Basic)

>Same day!? That's cool.

Ya but Mom feels a bit ripped off. Daughter stole her Birthday and now she has to share.<g>

>Update:
>
>1. Got Notification working on both the Hole object and the HoleList collection. Thta's cool. Modifiy the start angle, and it updates the Holes and that notifies the HoleList, and the HoleList notifies the ListView (I assume this is what is happening, because it does work)
>
>2. Got the converter working (http://learnwpf.com/Posts/Post.aspx?postId=05229e33-fcd4-44d5-9982-a002f2250a64)
> Lot's of code and hooking up just to make it work, but it does. Thank goodness for cut-and-paste.

Cool, they get easier to write once you get used to them, and you can do a lot of cool things with them. I found this in Marco's (MSDN Moderator) code, it makes is so you don't have to predeclare the converter in XAML:

    // Converter={x:Static cdsvc:cdsScaledValueConverter.Default}
    public static readonly cdsScaledValueConverter Default = new cdsScaledValueConverter();

If your using it a lot of the same converter the predeclare is probably better, but for single usage this is nice.

>3. Got the Toggle Visibility working by double clicking the row in the ListView.
>
>4. The HoleList is only fully regenerated if the HoleCount changes. Otherwise, I update each Hole as the BoltCirDia or StartAngle changes. It would be much less code just to do a full list.clear() with every change and regen it all from scratch, but I wanted to model it so that I work on the existing objects in the collection to updates them per the new inputs, rather than blowing them out and starting all each time.
>
>
>I'll keep working on it over the weekend and post updated XAML and code-behind Monday morning.

Look forward to seeing it.