|
Visible,TabStop,Auto properties are checked and all the others are unchecked.
|
|
|
|
|
|
Have you read the forum guidelines before posting the query.
And have you worked on VC++ before?
|
|
|
|
|
Dear all,
I am developing an application with VS2008, MFC 90.
There was an exception:0xC015000F: The activation context being deactivated is not the most recently activated one.I can not handle it.
The following is my call stack:
ntdll.dll!7c944a17()
[Frames below may be incorrect and/or missing, no symbols loaded for ntdll.dll]
ntdll.dll!7c944a17()
user32.dll!7e418734()
user32.dll!7e418bd9()
user32.dll!7e41885a()
user32.dll!7e418822()
user32.dll!7e4189cd()
> mfc90d.dll!AfxInternalPreTranslateMessage(tagMSG * pMsg=0x7e4189f0) Line 242 + 0x14 bytes C++
user32.dll!7e440457()
user32.dll!7e4196c7()
mfc90d.dll!AfxInternalPumpMessage() Line 183 C++
mfc90d.dll!CWinThread::PumpMessage() Line 900 C++
CapsvrTx.exe!CCapSvrRoot::LoadConfig(IUnknown * pICaller=0x00000000, int bRemoteSetup=1, int bMessagePump=1) Line 4716 + 0x20 bytes C++ // this is my function.
Your reply will be deeply appreciated. 
Best Regards.
Lance
|
|
|
|
|
Hi Lance,
I encountered the same issue 3 days ago with an MFC based application running on Windows7. I do not fully understand the problem but Junfeng Zhang over at Microsoft has described the situation which causes this error. You can read about it here:
SXS Activation Context --- Activate and Deactivate[^]
I was able to disable the exception by adding the following line in my Applications InitInstance().
afxAmbientActCtx = FALSE;
I do not know if there are any unwanted side-effects by adding this line. I am still researching the this issue.
Best Wishes,
-David Delaune
|
|
|
|
|
Did you ever find more info on this? I'm seeing a similar thing and setting that to FALSE also fixed it for me. Not sure what other side effects that might have though.
|
|
|
|
|
Hi Dave Calkins,
The 0xC015000F activation context error I experienced was easily avoided by adding the following line into my InitInstance() function.
afxAmbientActCtx = FALSE;
I did a bit of research into the subject and discovered that this boolean enables or disables the MFC internal SxS Activation Context[^] switching.
By setting this boolean to false your MFC application Module State Management[^] will not use the Activation Context[^] technologies. Essentially your MFC state management will work about as good as it did in older MFC versions.
Setting the boolean to false will not directly cause any problems. But unfortunately your MFC application loses benefits from SxS. This may or may not be a problem depending on whether your application uses multiple versions of the same library.
Welcome to DLL Hell[^]. 
Best Wishes,
-David Delaune
|
|
|
|
|
Hi All,
I am facing problem pretty much similar to Lance's one.My application crashes while closing.With a message "The activation context being deactivated is not the most recently activated one.". I tried the solution suggested in multiple replies to this issue, - adding the line afxAmbientActCtx = FALSE; to InitInstance();.But it didn't helped, the crash is still there.I tried to find any unhandled activation context but we do not have any left !!! Although we are saving xml files while closing the application.Any more ideas ? this is how the dump looks like --
> ntdll.dll!776e8b2e()
[Frames below may be incorrect and/or missing, no symbols loaded for ntdll.dll]
ntdll.dll!77733d60()
ole32.dll!75e101e5()
ole32.dll!75e10261()
ole32.dll!75e106fd()
ole32.dll!75dcc969()
msvcrt.dll!772f513f()
msvcrt.dll!772f50cf()
ole32.dll!75dc6cd4()
mfc90.dll!5ced3c82()
mfc90.dll!5ced3b22()
mfc90.dll!5d01e29f()
mfc90.dll!5ce99717()
mfc90.dll!5cedea57()
ole32.dll!75d7aa55()
ole32.dll!75dc6cd4()
mfc90.dll!5ced3c82()
mfc90.dll!5ced3b22()
mfc90.dll!5d01e29f()
mfc90.dll!5ce99717()
mfc90.dll!5cedea57()
ole32.dll!75d7aa55()
ole32.dll!75dc6cd4()
mfc90.dll!5ced3c82()
mfc90.dll!5ced3b22()
mfc90.dll!5d01e29f()
mfc90.dll!5ce99717()
mfc90.dll!5cedea57()
ole32.dll!75d7aa55()
Thanks In Advance
Sumit
|
|
|
|
|
Hi all,
I don't know if anyone is still having this problem, but..
Did any of you tried to figure out what unhandled exceptions occured?
I fixed my problem by switching on ALL Win32 exceptions. Found the issue in just minutes.
In VS 2005 or VS 2008; Debug -> Exceptions... (Ctrl-Alt-E) -> Check the option "Win32 Exceptions" (which enables all options in that branch)
Now start your app in debug mode in VS (Hit the F5 button). Look where it crashes now with an unhandled exception. Its just that simple 
Happy hacking,
Albert van Peppen
PS.
The use of "afxAmbientActCtx = FALSE;" should be avoided at all times because it will hide some issues which gonne bite you later on!
|
|
|
|
|
|
Thanks for the info, I appreciate it.
--
Kein Mitleid Für Die Mehrheit
|
|
|
|
|
Hey Jorgen,
Din valkomna
|
|
|
|
|
Hi,
With the help of Bacon Ultimate Chessburger
I changed my program or My Control Creation
Logic from ::Create to DDX_CONTROL
DDX_CONTROL in addition to Attaching the
Window object to the CWnd object
Subclass it
After the App Crashed with the Stack Overlow
right after exiting ::DoDataExchage
I went to the "CALL STACK" menu item
and noticed there were a number of calls
to AfxWndProc with message # 15
If I use DDX_CONTROL to Attach an Object
DO I have to provide that Dialog Control
A Message Map entry
|
|
|
|
|
can you paste your code here? you should create your dynamicaly created controls in OnInitDialog, not on DoDataExchange or in OnCreate cause maybe CWnd is not valid in that point
|
|
|
|
|
For the static controls I didn't have a unique
Identfier e.g IDC_STATIC for all my static
controls
DDX_CONTROL(pDX,IDC_STATIC,mycstatic)
DDX_CONTROL(pDX,IDC_STATIC,mycstatic1)
Once I gave each of them a unique identifier
e.g .IDC_STATIC1 IDC_STATIC2
the problem resolved
thankx
|
|
|
|
|
Hi friends,
I want to know why does an application class contain only one object in MFC. Plz tell me.
Thanks & Regards
Sairam
|
|
|
|
|
Because there is only one application in your application... 
If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler.
-- Alfonso the Wise, 13th Century King of Castile.
This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong.
-- Iain Clarke
[My articles]
|
|
|
|
|
In an executable, there must be one entry point that can be called by the loader, runtime etc.
There cannot be any ambiguity here.
That is why we can have only one main function in a console program and only one WinMain function in a windows program. And that is exactly why we can have only one CWinApp or CWinAppEx instance 'cause this class encapsulates the entry point for the executable.
«_Superman_»
I love work. It gives me something to do between weekends.
|
|
|
|
|
|
Hi,
I can give "transaction effect" with BitBlt() on Screen in case of Bitmap image.
but I'd like to know how to give "transaction effect" in case of jpg,gif and so on.
=== short example code ===
CDC MemDC;
BITMAP bm;
m_Bitmap.LoadBitmap(IDB_BITMAT1);
m_Bitmap.GetBitmap(&bm);
MemDC.CreateCompatibleDC(pDC);
CBitmap* pOld = (CBitmap*)MemDC.SelectObject(&m_Bitmap);
int w=bm.bmWidth;
int h=bm.bmHeight;
for(int j=0;j<w;j+=2)
{
pDC->BitBlt(0,0,j,h,&MemDC,w-j,0,SRCCOPY);
}
pDC->BitBlt(0,0,w,h,&MemDC,0,0,SRCCOPY);
MemDC.SelectObject( pOld );
Any comment will help me!
Thanks, have a day.
|
|
|
|
|
|
Bacon Ultimate Cheeseburger wrote: 1300 calories of pure beef goodness can't be wrong!
However you've to run for about twelve miles in order to consume them. 
If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler.
-- Alfonso the Wise, 13th Century King of Castile.
This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong.
-- Iain Clarke
[My articles]
|
|
|
|
|
Hi everybody, Happy Friendship Day to you all.
I want to know what is the main difference between OnDraw() and OnPaint(). Plz tel me in which cases they will be used?
Thanks & Regards
Sairam
|
|
|
|
|
OnPaint is the message handler for WM_PAINT.
Here you do any drawing on your window.
OnDraw is a virtual function for all view classes.
OnDraw is called by the OnPaint handler for each view to do its on-screen drawing.
OnDraw will also be called by the MFC framwork for printing in respose to WM_PRINT.
This is why OnDraw has a CDC parameter which specifies the DC on which to do the drawing.
This could be the DC of either the screen or the printer depending on where the drawing needs to be done.
«_Superman_»
I love work. It gives me something to do between weekends.
|
|
|
|
|
please suggest ur ideas??
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
