DOC/View/Mainframe or does it matter?
-
I am working on an SDI application (MFC) using the standard DOC/View/Mainframe created by Visual Studio 10. The application requires a special type of "Switchboard" consisting of basically CButtons. For whatever reason, I do not want to place the buttons in a conventional Dialog Box, but rather have them as children of DOC or View or Mainframe. This is my first time using DOC/View/Mainframe and my question is: Who should be the parent of these buttons, or does it matter at all from a program architecture convention standpoint? I am sure that Microsoft has this detailed, but I haven't a clue as to where to start looking. Thanks, Barry :confused:
-
I am working on an SDI application (MFC) using the standard DOC/View/Mainframe created by Visual Studio 10. The application requires a special type of "Switchboard" consisting of basically CButtons. For whatever reason, I do not want to place the buttons in a conventional Dialog Box, but rather have them as children of DOC or View or Mainframe. This is my first time using DOC/View/Mainframe and my question is: Who should be the parent of these buttons, or does it matter at all from a program architecture convention standpoint? I am sure that Microsoft has this detailed, but I haven't a clue as to where to start looking. Thanks, Barry :confused:
The view would ow the buttons. The document is, effectively, your model, so it will contain any data that you need.
*pre-emptive celebratory nipple tassle jiggle* - Sean Ewington
"Mind bleach! Send me mind bleach!" - Nagy Vilmos
CodeStash - Online Snippet Management | My blog | MoXAML PowerToys | Mole 2010 - debugging made easier