I can predict the next posting... "I ran your code and it never reached infinity what could the problem be?"
Why is common sense not common?
Never argue with an idiot. They will drag you down to their level where they are an expert.
Sometimes it takes a lot of work to be lazy
Please stand in front of my pistol, smile and wait for the flash - JSOP 2012
I know how to code a catch block, I was just wondering whether you had posted in the correct forum. When you catch the exception it should contain sufficient information for you to discover what went wrong in your code.
One of these days I'm going to think of a really clever signature.
To my knowledge, MFC does not contain tools for managing task transactions. There is no common framework for managing undos, redos, etc...
The try / catch mechanism is a simplistic implementation of such a system, built into C++ that allows a program to gracefully unwind from an aborted task. the Afx classes that support exception handling, simply build upon this framework.
I have seen articles that discuss transaction processing for the windows file system and other kernel elements, coming up in future releases, but at this time, I don't know much about it.
You'll likely find that you'll need to roll your own Transactional Tasks manager for your application.
I have a dll developed in c#, which does some interactions with a web service, this all seems to be fine. I have made the dll visible to COM. I then register the dll using regasm passing it a /codebase /tlb argument. Again all this works fine. I now get a tlb file. From here i reference the tlb in my VC6 project like so:
// Import the type library.#import "C:\\epos\\MyInterface.tlb" raw_interfaces_only
Once i compile the VC++ project i get a tlh file generated, which has the following contents (edited there is much more in this file just showing what is needed here):
I create COM earlier in the program so i have not included it in the code below.
Then i Create an instance of the c# class, to call the methods i need. Now this all works fine and i can call these methods and they work correctly.
Code in my Main.c file
IMyLinkPtr iPtrMyLink; //Global Variable
IChVRspPtr iPtrCheckVRsp; //Create the Interface to The CheckVoucher Responsevoid main()
short blnRetVal = 0; //Set to False Initially, return value from dll
IChVReqPtr iPtrCheckV(__uuidof(CChVReq)); //Create the Interface to The Method1 Class. This is another class in the dll
HRESULT hrRetval= E_FAIL;
hrRetval = iPtrMyLink.CreateInstance(__uuidof(CMyLink)); //This is the main class in the dll, a wrapper to call methods from.// Pass to the method the request class, a reference to the response class and a reference to the return value.
iPtrMyLink->CallMethod1(iPtrCheckV, &iPtrCheckVRsp, &blnRetVal);
The problem i am having is that my program crashes after some time where the memory has grown to 32mb, which to me is quite low. The crash occurs on a CreateInstance line, not necessarily the one above but some other method i have to another .net dll. My main question is about memory, before calling this line:
The memory in the VC6 app is 12mb, once this line is called the memory jumps to 24mb. Is this down to loading the .net Framework and if i have another dll that does the same the memory will jump to 32mb and will crash shortly after when attempting to create an instance again. I am releasing the objects so im not sure what is going on here.
OK, this is a bit of a long shot, but any help would be appreciated...
I have a CWnd that contains a CHeaderCtrl and CTreeCtrl within a CDialog within a CScrollView within a CSplitterWnd within a CControlBar.
All works very well except the CWnd border (ClientEdge) is not redrawn (just seems to leave whatever was underneath) when splitter bar is moved, and CWnd is resized and invalidated. However, the edges ARE redrawn properly when the whole app is resized which also resizes panes in CSplitterWnd and subsequently CWnd in excatly same way as above. In other words, both scenarios call CSplitterWnd::RecalcLayout() which trickles down and drives all resizing of child view/dialog/window/tree control. The only difference I can really see is that one was generated by resizing whole app, while other was generated by StopTracking() of the CSplitterWnd. All other controls (buttons, group boxes, etc. resize and redraw fine).
A lot of web crawling suggests perhaps that it's something to do with being on a CControlBar which may result in some notify commands not getting to all children? But
I've tried trapping the paint messages, but am a bit confused as OnPaint seems to be being called...I'm now assuming that the window border isn't actually drawn by OnPaint? If it's not, where is it drawn and by whom?
Just playing around with painting in OnEraseBkgnd, I've noticed something very strange...if I get client rect and paint the background red, in the case where it's not repainting correctly, only an area at either end of the scroll bars to the right of the tree control are being painted red, where as in the case where it is working, the whole control is being painted red - the client rects are always same size.
Invalidating the CWnd doesn't fix the problem. Calling InvalidateRect(NULL) invalidates the whole screen which does fix the repainting, but is not a viable solution as there are graphs on the other bits of the screen that can take several seconds to redraw and shouldn't be redrawn any time the splitter bars are moved.
Anyone ever seen anything like this? I'm extremely confused and any pointers as to things to try would be much appreciated.
BTW - dialog in view in splitter wnd in ccontrol bar is part of a function panel down one side of the app.
"He is no fool who gives what he cannot keep to gain that which he cannot lose.
OK, while I've no idea why this happens, I've found a solution.
I've read up that OnNcPaint handles the borders (NC being Non-Client area). And it's this WM_NCPAINT message that never arrives in the situation where the border isn't painted. While I've no idea why this message isn't sent, sending a WM_NCPAINT message to the control after it's been resized ensures the frame is always repainted. Success!
"He is no fool who gives what he cannot keep to gain that which he cannot lose."