Re: How to work with XML in MFC?
"Daniel James" <wastebasket@nospam.aaisp.org> wrote in message
news:VA.00001626.2e2424a1@nospam.aaisp.org...
I wouldn't do that ... Like Mihai I like the fact that the controls you
get in an MFC dialog are system controls. I also like the fact that the
vanilla resource compiler is used to build resources, and so keep some
compatibility with other tools (for other languages and from other
vendors).
However, there's no reason why the IDE shouldn't allow the programmer
to specify additional properties that can be set by wizard-generated
C++ code when the dialog is instantiated. That would only happen if the
programmer chose to override the default properties from the .rc file,
of course -- otherwise the controls will be default native control
behaviour.
Sure, that would work as well. I don't much care where the font info is
stored as long as it is seemless to edit and work with.
OTOH ... a dialog is a dialog ... most of the time it would be wrong to
change the fonts of controls withing the dialog on a whim. An app's
user interface should be consistent and should conform to UI design
guidelines. If a font is to be changed it should be changed on a
system-wide basis (perhaps for accessibility reasons) not just because
the programmer thought it would be "cool" to use italic labels.
It's generally an error to want to alter control fonts individually.
I typically use a bold version of the default dialog font for labels and
such. That works well. In fact it's so common to do that these days, if
you don't do it, your app looks so 1990's. You know, like a default MFC
app! :-O
Thanks,
David