winapi - Best way to handle dialog population? -
In my application, I have a large set of objects and children, I am preparing a set of property sheets, Which you can open to inspect a particular object (and this is a base class) so that you can modify them directly.
What is the best strategy to popularize these dialogues? To test the existing object on the current design dialog, and intent the desired property sheet for those items that you want to inspect. In WM_INITDIALOG of each property sheet, there is a specific code to get / set each member variable.
The potential problem I have seen here is that everything is difficult in a single source file that could potentially be quite large. I am thinking of offloading the communication population in each individual object, but I am surprised that typing the UI code in our back-end object code is a wise idea. Future maintenance is required to travel instead of a source file rather than a number of different objects in a different source files.
Any one of the best practices I can get from here? I'm not sure where to begin with I am fine to continue with the current design, but since I talk with these items, I'm in a position to redraw, so I want to make the right choice here. I am
Comments
Post a Comment