Today, My Jurisdiction Ends Here

[billroper]

Well, actually, no. It doesn't.

As we try to push our product to completion, I have inherited Somebody Else's Dialog(TM). I am pretty good at writing MFC DDX/DDV code that does what MFC expects us to do when making sure that the data the user has entered is correct.

Somebody Else's Dialog(TM) is using a unique method of doing data validation that appears to have been completely borked by the change to the new version of MFC as we moved to Visual Studio 2010. So I'm fixing up the data validation so that it does what MFC expects us to do. And as I do that, Somebody Else's Dialog(TM) stops throwing up an endless succession of file dialogs and message boxes before we even get a chance to enter data.

*sigh*

Oh, well. As far as Somebody Else's Dialog(TM) is concerned, there's a new sheriff in town...

Comments

[poltr1]

Windows programmers are still using MFC? I thought that morphed into .NET over the past several years.

(Shows you what I know about Windows application programming.)

[billroper]

There's a lot of .NET going on (including here), but we started writing this product on MFC back in 1994 and the underpinnings (and large chunks of the interface) are still written in MFC.

[catsittingstill.livejournal.com]

Whuf.

This sounds like a lot of work. Good luck with it.

[billroper]

Thanks! Finally fixed now, I think. :)

[purpleranger.livejournal.com]

When you say "completely borked," are we talking about Swedish Chef "bork bork bork"? Just wanting to be clear on this.

[billroper]

The code looked like the Swedish Chef had been at it, yes...

[purpleranger.livejournal.com]

Are you at the point where you can say, "The code is okey-dokey"?

[ericcoleman]

Hmmm, maybe we'll watch that movie tomorrow

[billroper]

A fine choice!

[jebra.livejournal.com]

The subject line made me smile. Not being a Super Bowl fan, I may spend tomorrow watching that movie again.

[billroper]

Yeah, I always liked that film...