C / C++ / MFC

Problem with closing program

5-Jun-07 6:01

Jooooe wrote:
is vc still the language to learn...

If you need to.

Jooooe wrote:
which the most used language these days

How could anyone possibly know the answer to this? Roll eyes | :rolleyes:

"A good athlete is the result of a good and worthy opponent." - David Crow

"To have a respect for ourselves guides our morals; to have deference for others governs our manners." - Laurence Sterne

Re: VC or not VC

Matthew Faithfull5-Jun-07 6:04

Matthew Faithfull

5-Jun-07 6:04

If you ask in here you know you're going to get the answer VC++ Big Grin | :-D

After all you're not a soft headed newbie who need his memory managed for him are you? Seriously it all depends on what you want to do, how much control you want over how it's done and how quickly you want it done.

Nothing is exactly what it seems but everything with seems can be unpicked.

Re: VC or not VC

bob169726-Jun-07 6:01

bob16972

6-Jun-07 6:01

Jooooe wrote:
which the most used language these days

www.tiobe.com keeps statistics on programming language search engine queries. As Mr. Crow stated, it is unlikely that this will be an accurate representation of what is used most as nobody could possibly know that, but it gives one a picture of how often a person resorts to a search engine query for a particluar language.

One could argue since MSDN is so thorough, that there will be fewer queries from users using Microsoft compilers which would indicate the statistics are probably less than accurate. One could also argue that the statistics merely indicate which languages require secondary assistance to get things done and could simply indicate a flawed help system for the leading compilers of that language.

Beware of buzzword fluctuations as they usually reflect the initial surge of queries to find out what a buzzword technology is. Those tend to taper off after the first year for newer technologies.

KellyR5-Jun-07 5:29

5-Jun-07 5:29

Hi,

This program is a dialog-based MFC application.

My problem is that when I click the "X" in the top right corner of the program to close it, only the window closes, but the process remains running.

I'm not very familiar with MFC (I usually use standard Windows API) so I don't know how to catch the WM_SYSCOMMAND message to handle this. I've tried ON_WM_SYSCOMMAND() in the message map, but I get a compiler error since neither of my two classes are inherited from CWnd objects (one is CWinApp, the other is CDialog).

Does anyone know why my program isn't closing, or how could I catch the WM_SYSCOMMAND message so I could force it to close?

Thanks!

David Crow5-Jun-07 5:38

Re: Problem with closing program [modified]

5-Jun-07 5:38

KellyR wrote:
...but the process remains running.

How are you verifying this? Have you created additional threads?

"A good athlete is the result of a good and worthy opponent." - David Crow

"To have a respect for ourselves guides our morals; to have deference for others governs our manners." - Laurence Sterne

KellyR5-Jun-07 7:06

5-Jun-07 7:06

The process is still visible in the task manager, and no I only have a single thread.

Mark Salsbery5-Jun-07 7:21

5-Jun-07 7:21

How and where is the main dialog created?

BTW, CDialog IS a CWnd Smile | :)

Mark

"Posting a VB.NET question in the C++ forum will end in tears." Chris Maunder

KellyR5-Jun-07 7:29

5-Jun-07 7:29

I thought so too but for some reason I still get a compiler error when I try to map ON_WM_SYSCOMMAND() in my dialog; I guess that's because the BEGIN_MESSAGE_MAP macro ties my class to CDialog and not CWnd? Sorry if I sound like an idiot, I'm just not that familiar with how MFC works. This is the first MFC application I've ever created from scratch so I'm still getting the hang of it.

The main dialog is created in the InitInstance() of the main application.

So something like this:

BOOL CTheApp::InitInstance()<br />
{<br />
  CWinApp::InitInstance();<br />
  m_MainDlg = new CMainAppDlg();<br />
  <br />
  if(!m_MainDlg->Create(IDD_MAIN_DIALOG))<br />
  {<br />
    AfxMessageBox(TEXT("Failed to initialize."), MB_OK, 0);<br />
    return FALSE;<br />
  }<br />
  m_MainDlg->SetWindowText(TEXT("Test Dialog"));<br />
  m_pMainWnd = m_MainDlg;<br />
<br />
  return TRUE;<br />
}

Mark Salsbery5-Jun-07 7:43

5-Jun-07 7:43

What's the compiler error when you add a ON_WM_SYSCOMMAND() entry to the dialog class'
message map?

Mark

"Posting a VB.NET question in the C++ forum will end in tears." Chris Maunder

KellyR5-Jun-07 7:51

5-Jun-07 7:51

The error is this:

error C2440: 'static_cast' : cannot convert from 'void (__thiscall CMainAppDlg::* )(void)' to 'void (__thiscall CWnd::* )(UINT,LPARAM)'

Mark Salsbery5-Jun-07 7:57

5-Jun-07 7:57

Your handler function needs to be declared as

afx_msg void OnSysCommand(UINT nID, LPARAM lParam);

From the error message it looks like you have void OnSysCommand();

"Posting a VB.NET question in the C++ forum will end in tears." Chris Maunder

KellyR5-Jun-07 8:04

5-Jun-07 8:04

Oh, duh.. thanks!

Mark Salsbery5-Jun-07 8:21

5-Jun-07 8:21

I'm still not sure why the app isn't shutting down - I thought CWnd::OnNcDestroy() took
care of that if the window is the app's main window (designated by setting m_pMainWnd in
InitInstance()). Maybe debugging a breakpoint there will explain it.

Mark

"Posting a VB.NET question in the C++ forum will end in tears." Chris Maunder

David Crow5-Jun-07 10:08

5-Jun-07 10:08

Is this a dialog-based application? If so, then why are you creating a modeless dialog?

"A good athlete is the result of a good and worthy opponent." - David Crow

"To have a respect for ourselves guides our morals; to have deference for others governs our manners." - Laurence Sterne

Michael Dunn5-Jun-07 19:23

Michael Dunn

5-Jun-07 19:23

You don't handle the [X] button with WM_SYSCOMMAND, you handle WM_CLOSE. More commonly, in a dialog-based app, you don't handle WM_CLOSE, but instead WM_COMMAND with a command ID of IDCANCEL. That way, your app will properly implement the three ways of closing a dialog: a button whose ID is IDCANCEL, the [X] button, and the Esc key.

--Mike--
Visual C++ MVP Cool | :cool:

LINKS~! Ericahist | PimpFish | CP SearchBar v3.0 | C++ Forum FAQ

Dunder-Mifflin, this is Pam.

Heap error

simoncoul5-Jun-07 5:27

simoncoul

5-Jun-07 5:27

Hello, I'm trying to allocate some memory but for some reason it keeps giving me a heap error. If I just continue through it in debug mode the function will output the proper number, and any time after that it continues to output numbers without and error, untill I restart visual studio then I get the error again. The error always occurs with h=2, any info on where to get start or how to fix this would be great.

const Complex I(0.0L,1.0L); //imaginary numbers

double **I = (double**)malloc(sizeof(double*)*K);
for ( h =0; h < K; h++){
	I[h] = (double*) malloc(sizeof(double)*K);
}

Thanks

David Crow5-Jun-07 5:37

5-Jun-07 5:37

Since Complex is a class, you should probably be using new (and delete).

simoncoul wrote:
const Complex I(0.0L,1.0L); //imaginary numbers
double **I = (double**)malloc(sizeof(double*)*K);

So what is I?

"A good athlete is the result of a good and worthy opponent." - David Crow

"To have a respect for ourselves guides our morals; to have deference for others governs our manners." - Laurence Sterne

simoncoul5-Jun-07 5:44

simoncoul

5-Jun-07 5:44

This code was produced by someone else, but from my taking on it, it's just a 2D array with 1000 positions. I don't believe that I needs to be complex either, since it is being cast as a double, and no calculations are done with that involve it needing to be complex.

Thank you

David Crow5-Jun-07 10:22

5-Jun-07 10:22

But what is I? How is the compiler not complaining about a re-definition?

"A good athlete is the result of a good and worthy opponent." - David Crow

"To have a respect for ourselves guides our morals; to have deference for others governs our manners." - Laurence Sterne

Matthew Faithfull5-Jun-07 5:50

Matthew Faithfull

5-Jun-07 5:50

I can't tell you why you're getting an erro on h == 2 but I would try something like this instead.

<br />
double** I = new double*[K];<br />
for( int h = 0; h < K; h++ )<br />
{<br />
  I[h] = new double[K];<br />
}<br />

Obviously you'll need to do matching deletes, remember to use delete [], array delete in case you every want to compile this on a non Microsoft system.

Nothing is exactly what it seems but everything with seems can be unpicked.