I know that but the monkey can't seem to understand it. Changing subjects, the voting in this thread is a perfect example of how off it can be, my actual (and correct) answer to the question get's no votes but my post flaming someone else get's a '5' :laugh: :laugh:

Okay I'll check them up. Thanks for your responses.

DavidCrow wrote: Have you bothered to read the documentation? The fifth argument is the ID. :doh: . Please excuse. That's dumb. Thanks for the reply.

grassrootkit wrote: I knew my question was not clear this time.Sorry. Actually I understood what you said in your last reply. I was talking in context with the 0 size files. "Assuming I'm opening the 0 size file" and trying debugging, trying to catch the call stack. etc. Anyway helped enough already. (Back on AC now!) You're quite right - it doesn't bother calling serialize for zero byte files - makes sense, I guess. Java, Basic, who cares - it's all a bunch of tree-hugging hippy cr*p

Being forgetful is a common...erm...what's it called...umm...sympthom by programmers, because...umm...erm...what were we talking about again? :D > The problem with computers is that they do what you tell them to do and not what you want them to do. < > Life: great graphics, but the gameplay sux. <

:doh: He is no different. Just looked at his profile.

Well, you would need to tell the dialog about the document. You could add a CDocument* member variable to the dialog and set it before you call DoModal. Alternatively (and I prefer this one), just pass the relevant attributes of the document to the dialog, so the dialog doesn't need to know about the document - letting the dialog have visibility of the document class upsets my aesthetic sense. Java, Basic, who cares - it's all a bunch of tree-hugging hippy cr*p

Stuart Dootson wrote: The word 'global' always rings alarm bells lol yes that would. Actually I planned to bring it in into the design. But to quickly explain you about what I thought I meant them as global. :) Anyway thanks a lot.. let me get into the lab :D.

The tree control has the Has Buttons and Has Lines properties that you must set to true in the resource editor. «_Superman_» I love work. It gives me something to do between weekends.

grassrootkit wrote: When you open a new file using the File->Open menu, where's the event handled? I mean I would like to see the place where it creates the CFileDialog & does a DoModal(). That happens deep within the bowels of MFC, not at your application level. "Old age is like a bank account. You withdraw later in life what you have deposited along the way." - Unknown "Fireproof doesn't mean the fire will never come. It means when the fire comes that you will be able to withstand it." - Michael Simmons

Hey got it :).. I've used COM but not from a C++ client. So my first C++ client takes off well :D. :jig: thanks. Next is to use Connection points in a C++ client. ;) Can you point to a good article that speaks about USING connection points in a C++ client? modified on Friday, February 20, 2009 5:41 AM

As I've said in my other reply - I think you should probably leave handling OnFileOpen to CWinApp, a) because it fits better with the model of responsibilities and collaborations the MFC doc/view framework was designed around, and b) it fits with MFC, so you don't need to write as much code! Java, Basic, who cares - it's all a bunch of tree-hugging hippy cr*p