Re-creating a MFC application

[fasterwego]

I have a MFC application that I'm trying to recreate in C#, but I've
run into something of a problem.

In the MFC app, I have a window that captures the change of any
control in that window. It then sets itself to "edit mode", disabling
certain buttons, etc.

In C#, I don't really see a way to do this aside from assigning one
event handler to every control on the form that will capture that
control's "Changed" event. This seems terribly manual. Is there
another way to do this that I don't see?

Thanks for any help.

 

[Simon Tamman]

Why do you need to know when the controls have had their value changed?
Could DataBinding do the job for you instead?

 

[VJ]

How did u do it in MFC ?? Like inform the window that a control in window
has changed..

VJ

 

[PFC Sadr]

Dude I could do that in Access in about 2 minutes

maybe you should stop using obsolete langauges-- and start using VB

I mean seriously here.. you're jumping from C to C#?

GET A CLUE DIPSHIT

 

[Simon Tamman]

Don't be a dick.
He's upgrading an EXISTING MFC application to .NET. Therefore he needs to
find the equivalent .NET calls for the MFC code.
As it stands you can use C++ (for some applications a better language than
C# or VB.NET) to use MFC not just C.

Did you also realise that most of everything we use sits ontop of C
libraries. The whole Windows platform is propped up by these "obselete" C
libraries.
While C might not have the toys of OOP or the other fun we have in .NET land
it is still fundamentally a more important language than the high level
frameworks we use.

Either way, if you're not going to attempt to help the person in the
newsgroups or have anything interesting or useful to say then DONT POST.

Simon

 

[aaron.kempf]

I'll post when and where I want

C is obsolete; anyone that uses it is ****ing stupid
C++ is obsolete; anyone that uses it is ****ing stupid
C# is obsolete; anyone that uses it is ****ing stupid


I'm so sorry that when all the kids saw C# they thought 'holy crap we
can use a crap language _AND_ have a decent interface'

I mean seriously

just because C finally has an interface that is comparable to VB; that
doesn't mean that C is going to have a great homecoming

**** C AND ANYONE THAT USES IT

VB won the war; kids

 

[aaron.kempf]

and for the record; who gives a shit about OOP?

it makes your code HARDER TO READ, MORE VERBOSE, AND EXECUTE MORE
SLOWLY

I have that; in writing-- from MS press

 

[Simon Tamman]

I apologise to anyone that isn't here for flaming and apologise profusely to
fasterwego for sidetracking his subject but I'm afraid i've been tempted by
the troll bait.

I've just got to say.
hahahahahahahahahaha.

He writes in VB, and he calls us Dim.

Isn't the VB framework built on MFC (or at the very least C libraries)?
Didn't M$ drop VB in favour of the OOP version VB.NET?

and for the record; who gives a shit about OOP?

it makes your code HARDER TO READ, MORE VERBOSE, AND EXECUTE MORE
SLOWLY

I have that; in writing-- from MS press

I'll post when and where I want

C is obsolete; anyone that uses it is ****ing stupid
C++ is obsolete; anyone that uses it is ****ing stupid
C# is obsolete; anyone that uses it is ****ing stupid


I'm so sorry that when all the kids saw C# they thought 'holy crap we
can use a crap language _AND_ have a decent interface'

I mean seriously

just because C finally has an interface that is comparable to VB; that
doesn't mean that C is going to have a great homecoming

**** C AND ANYONE THAT USES IT

VB won the war; kids