2 replies to this topic

[gaconga1105]

In MFC programming, any added resource has its own ID,
ex:

#define IDD_DIALOG 105

and the class also has an enum to specify it (I think),
ex:

class MyDialog : public CDialog

{

  public:

   enum { IDD = IDD_DIALOG}

}

     

I wondered that, if we have to create tons of different Dialogs, or simpler, Buttons, we also have to create tons of different class with tons of different enum??? :confused:

This may be a stupid question, but thanks for any help
Bim Bim

[Ancient Dragon]

Microsoft compilers IDE such as VC++ 2010 handles all that for you. When you add a button to a dialog the IDE will generate the ID for you. You don't have to manually create all that stuff.

[kernelcoder]

That practice is a pattern in MFC. So, I think if you have time to create tons of classes, you would have time to define an enum for that class.