After quite some time I finally tried out your suggestion today and it seems to solve my problem. Thank you so much!

Answering myself: Both applications seem to use different implementations of the new operator - despite both using the MFC: Application 1 uses the one from the CRT and throws a std::bad_alloc exception. Application 2 uses the one from the MFC and throws a CMemoryException*. According to "Binglong's Blog" (link see below) the actual choice which new operator will be used depends on (quote) "the operator new comes from the library the linker sees first". Ugh. What a mess. Unfortunately I was not able to define myself what "the linker sees first". If somebody has a handy hint, go ahead, will be very apprectiated! In addition to that there seems to appear some "Microsoftic Magical Trick": in case a CException is thrown ""somebody"" checks whether it will be catched - if yes, it the exception will be thrown, if not, the application will not simply crash but a message box will be displayed and the application can run on. Please note that this is an assumption based on my observation and to be honest I don't consider it helpful to wastespend more time on examining that behaviour further. Helpful links: Binglong's space: Operator new, STL memory allocator, and MSVC[^] Visual C++ 6.0: Don't Let Memory Allocation Failures Crash Your Legacy STL Application[^] Visual C++ exception handling[^]

As far as I can see that value is only the predefined, initially reserved memory for the stack. At least for all my applications SizeOfStackReserve is 1048576 Bytes (= 1 MB) and SizeOfStackCommit is 4096 Bytes. I've gathered that information with the following code which analyses .exe files: http://support.microsoft.com/default.aspx?scid=kb;EN-US;q90493 I'd like to know how big at a certain point during runtime my stack is... -- modified at 6:54 Wednesday 29th March, 2006

Thank you so much guys! Sometimes I just need a nudge in the right direction X|

please refer winuser.h where you can find the numeric values of each windows message example: #define WM_COMMAND 0x0111 #define WM_SYSCOMMAND 0x0112 #define WM_TIMER 0x0113 #define WM_HSCROLL 0x0114 #define WM_VSCROLL 0x0115 #define WM_INITMENU 0x0116 #define WM_INITMENUPOPUP 0x0117 #define WM_MENUSELECT 0x011F #define WM_MENUCHAR 0x0120 #define WM_ENTERIDLE 0x0121

I want to save me the time to learn the wiki markup and use what I know instead (BB-code) so I really do not intend to spend the time to make me a new/modified wiki myself... Basically I need/want an online "scribble space" where I can put down notes as easily and fast as possible, just when they come to my mind and regardless where I am (as long as I have internet access...). "fast and easy" are the keywords and even with all the setup I don't want to spend to much time. Hmm... Thanks anyway, T.T.H.

Thank you so much, Mike! :)

That is because the View never moves... The view window is actually a child window of your CChildFrame (from CMDIChildWnd), and (almost) always sits at (0,0). When you drag the "View" about, you are actually dragging the frame about. The view sits still relative to its parent window. When you resize the "View", you actually resize the frame. The frame resizes the View, which is why you get WM_SIZE messages! If you really need to know that you've moved, move your functionality into CChildFrame. The child frame can be useful, as you can (e.g) toolbars to each frame, instead of just having the main ones. Hopefully that made sense! Iain.

Concerning 1: I solved the problem another way and don't have multiple document templates now - so I don't need to preselect one of them. Concerning 2: I want to switch through all the views by some buttons on the toolbar. I guess I developed a solution yesterday solving my problem. I appended a (quite long) post under Jorge's articel about switching views. You can find it here. Thanks for the help, Matthias / T.T.H.

Thanks for suggestions, I use 7zip now. Haven't seen its GUI yet but console usage is simple. That I was looking for :) T.T.H.

It compiles on VC 7.1. Kevin

Thank you very much for the precise answer, this exactly solved my problem! T.T.H. - *happy* :)

For date and time use the __DATE__ and __TIME__ macros. Not sure how to help you with USER and MACHINE NAME yet. Kind regards, Tim