Jump to content
  • Advertisement


This topic is now archived and is closed to further replies.


Integration or Encapsulation :: MFC

This topic is 5982 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

Hi. I have a question about software design pertaining in particular to MFC and Windows programming in general. Windows programs rely heavily on messages. Objects sends and receive messages. Is it conventional to keep classes independent one of one another and/or is it conventional to integrate all classes and objects into on system of classes? For example, I have a simple doc/view (SDI) program. There is a function in doc called Divide(). This function performs a divide of two integers. Now, let say I have a dialog box that requires the use of division. The difference is that the dialog box is not meant to perform division. It requires division for another purpose. In the case above, is it conventional to send a message back to main frame and then redirect the message to doc to perfect the division? Is it conventional to just create a new function for that dialog box? If it is conventional to create a new function for the dialog box, then how about if the similarity is a structure, or a class? Messages in Windows open up new doors for programmers allowing programmers to try out more tools. Thanks, Kuphryn

Share this post

Link to post
Share on other sites

  • Advertisement

Important Information

By using GameDev.net, you agree to our community Guidelines, Terms of Use, and Privacy Policy.

We are the game development community.

Whether you are an indie, hobbyist, AAA developer, or just trying to learn, GameDev.net is the place for you to learn, share, and connect with the games industry. Learn more About Us or sign up!

Sign me up!