C / C++ / MFC

Rajesh R Subramanian23-Jul-09 9:53

23-Jul-09 9:53

How hard is it to add MFC support to the console application and send a message to it so that it reads the new file again in response to the message? I understand you are having a trouble communicating from your MFC app to the console app?

It is a crappy thing, but it's life -^ Carlo Pallini

rahuljin23-Jul-09 10:09

rahuljin

23-Jul-09 10:09

the win32 application is not a console application. i dont know how to communication between the two application can be set.

in vs2008, i used win32 project (not win32 console application) for creating the win32 application. also the header files used are ---

#include <windows.h>
#include <winsock.h>
#include <tchar.h>
#include <wchar.h>
#include <iostream>
#include <fstream>
#include <shlwapi.h>

Re: [mfc] restart other process [modified]

ThatsAlok23-Jul-09 20:00

ThatsAlok

23-Jul-09 20:00

Does you application contain or create a window. If yes, you can use Window Messaging to communicate between two application, just add common message id between two application, and related function in WndProc function for win32 application and between BEGIN_MESSAGE_MAP and END_MESSAGE_MAP for MFC application.

"Opinions are neither right nor wrong. I cannot change your opinion. I can, however, change what influences your opinion." - David Crow
Never mind - my own stupidity is the source of every "problem" - Mixture

cheers,
Alok Gupta
VC Forum Q&A :- I/IV
Support CRY- Child Relief and You

rahuljin23-Jul-09 21:57

rahuljin

23-Jul-09 21:57

there is no create window function in the win32 application. there is only messagebox().

modified on Friday, July 24, 2009 4:12 AM

Rajesh R Subramanian23-Jul-09 21:08

23-Jul-09 21:08

You could send the win32 app a message and a message handler to it. There are several tutorials on IPC in CP, just take a look at those.

It is a crappy thing, but it's life -^ Carlo Pallini

ThatsAlok23-Jul-09 19:48

ThatsAlok

23-Jul-09 19:48

Rajesh R Subramanian wrote:
How hard is it to add MFC support to the console application and send a message to it so that it reads the new file again in response to the message

Can't u send message to Win32 application ?

cheers,
Alok Gupta
VC Forum Q&A :- I/IV
Support CRY- Child Relief and You

Rajesh R Subramanian23-Jul-09 21:07

23-Jul-09 21:07

Not if it is a console application.

It is a crappy thing, but it's life -^ Carlo Pallini

ThatsAlok23-Jul-09 22:38

ThatsAlok

23-Jul-09 22:38

Rajesh R Subramanian wrote:
Not if it is a console application.

Humm... we can send window message to container window then Smile | :)

cheers,
Alok Gupta
VC Forum Q&A :- I/IV
Support CRY- Child Relief and You

ThatsAlok24-Jul-09 1:14

ThatsAlok

24-Jul-09 1:14

Sorry if my comment hurt. That’s not intentional.. i think you felt bad.. my apology!

cheers,
Alok Gupta
VC Forum Q&A :- I/IV
Support CRY- Child Relief and You

Rajesh R Subramanian24-Jul-09 6:15

24-Jul-09 6:15

I don't see what's there in your post to hurt me. I also don't know why do you felt that I was hurt. Smile | :)

It is a crappy thing, but it's life -^ Carlo Pallini

Exception Error.

FISH78623-Jul-09 5:20

23-Jul-09 5:20

Can Someone help I am not sure whats wrong.

I am getting the following debug message:
First-chance exception at 0x5d0c373e in Capture Data.exe: 0xC0000005: Access violation writing location 0x0043454c.

However on exit I get:
The program '[1284] Capture Data.exe: Native' has exited with code 0 (0x0).
Here is the code I have used:

BOOL CCaptureDataApp::InitInstance()
{
InitCommonControls();
CWinApp::InitInstance();
CCaptureDataSheet sheet("My Very Own Property Sheet App",NULL,0);
sheet.m_psh.dwFlags |= PSH_NOAPPLYNOW;//hide apply button
m_pMainWnd=&sheet;
INT_PTR nResponse=sheet.DoModal();
return FALSE;

In the Capture Data Sheet

IMPLEMENT_DYNAMIC(CCaptureDataSheet, CPropertySheet)
CCaptureDataSheet::CCaptureDataSheet(UINT nIDCaption, CWnd* pParentWnd, UINT iSelectPage)
	:CPropertySheet(nIDCaption, pParentWnd, iSelectPage)
{
	AddPage(&m_Page01);
	AddPage(&m_Page02);
}

CCaptureDataSheet::CCaptureDataSheet(LPCTSTR pszCaption, CWnd* pParentWnd, UINT iSelectPage)
	:CPropertySheet(pszCaption, pParentWnd, iSelectPage)
{
	AddPage(&m_Page01);
	AddPage(&m_Page02);
}

CCaptureDataSheet::~CCaptureDataSheet()
{
}
BOOL CCaptureDataSheet::OnInitDialog()
{
	BOOL bResult = CPropertySheet::OnInitDialog();
}

Code-o-mat23-Jul-09 6:17

23-Jul-09 6:17

I don't know why you get that exception but try turning on "Break into debugger on exceptions" in Visual Studio, it might show you where exactly the exception gets thrown. (In VS2003 it's under Debug->Exceptions in the menu)

> 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. <

FISH78623-Jul-09 6:32

23-Jul-09 6:32

This is where i am stuck in the debgugger. Not sure whats happening?

BOOL AFXAPI AfxDeactivateActCtx(DWORD dwFlags, ULONG_PTR ulCookie)
{	
	BOOL rc = pfnDeactivateActCtx != 0 ? pfnDeactivateActCtx(dwFlags, ulCookie) : FALSE;
	return rc;
}

Why would it exit with a 0 if I haven't changed anything else in the code?
Would it not give me a memory leak or something?

FISH78627-Jul-09 3:37

27-Jul-09 3:37

http://msdn.microsoft.com/en-us/library/0bw65cxb(VS.80).aspx[^]">

This article states to ignore the return value from the CPropertySheet Class, unless I mis-understood it.

Does that mean I ignore the exception as well?

Code-o-mat27-Jul-09 3:40

27-Jul-09 3:40

Don't know but i doubt it.

> 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. <

FISH78628-Jul-09 10:22

28-Jul-09 10:22

I am sorry I am not trying to be a pain. This is frustratung me...
Here is what I did...Any suggetions...
On a different machine i went down in versions..from 2008-2005-and finally to VStudio 6.
I used the same steps in all ..I got the same exception error except in Vstudio 6..Where I got no exception error...Imported the same project into my Visual Studio 2008 and it works fine...No First-chance error.

I am not sure what to do?...Well for now I can work with this imported project...but is this really a solution?...I have come to the end of the rope on this one...If I did something wrong, would VStudio 6 not complain as well?

Do you think you can advice me as what to do? I don't like to give up, at the sametime I don't want to be hitting my head if it is a bug in VStudio 2008?

I can't see me to be the only one trying or using the property sheet based application?

Thanks, I will really appreciate some sort of feed back, I am new at this and it's frustrating me..Please advice.

Code-o-mat28-Jul-09 10:46

28-Jul-09 10:46

Is it possible that maybe all your project needed was a complete rebuild?

> 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. <

FISH78628-Jul-09 11:09

28-Jul-09 11:09

I did 3 different projects and with all I did a rebuild..
thinking of the same thing?

Code-o-mat29-Jul-09 0:24

29-Jul-09 0:24

Yes, i am just clueless how importing the very same project from 6.0 would solve your problem...
So you say the exception is thrown from AfxDeactivateActCtx? I supose that the pfnDeactivateActCtx pointer is pointing at something it shouldn't be. Can you maybe try to track down where this gets a value assigned? Maybe whatever it is pointing at gets destroyed somewhere and then the pointer is not NULL-ed out...

> 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. <

FISH78629-Jul-09 9:36

29-Jul-09 9:36

I am getting it in disassembly.

Code-o-mat29-Jul-09 9:41