Re: Is Doc/View Architecture really needed?
The MFC wizards will generate the Doc/View for you. If that code won't
compile then you have other issues. It's always worked for me.
The function of a view is essentially a window to your document. Generally,
this is your main window, or in the case of an MDI application, one of the
main child windows. Basically, a view should display the associated
document.
I've used the splitter window too without much trouble.
I ABSOLUTELY use the MFC wizards to create my initial application every
single time I use any part of MFC. You should do this and verify what is
created will compile. If it does, try one thing at a time. If something
doesn't work, you can ask about it here.
--
Jonathan Wood
SoftCircuits Programming
http://www.softcircuits.com
"sawer" <sawer@discussions.microsoft.com> wrote in message
news:BFD7466A-4323-459D-89F0-E26191384360@microsoft.com...
There were many errors, some of them about header files.
Some of them run-time errors and one of them is about can not start
without
empty document.. something like that. I don't remember well.
To be honest , i still don't understand what is the function of CView
class.
I tried to use splitter window. But it is very painful with MFC. I ignored
doc view, everything resolved. Like here:
http://www.codeproject.com/useritems/SplitWindow.asp
Now i can finish my GUI. It is very simple GUI. But i really spent to much
time with MFC wizard codes. I modifed code too much to avoid errors so i
think myself why i didn't start empty project and wrote at the beginning.
I asked this because of this problems.
Class view, Properties window, add function etc.. are very useful. But
what
about MFC Application wizards code?
Do you really use it?
or Do you start empty project?
thanks for all answers.