C / C++ / MFC

Closing Program, shutting down c++ win32.

13-Jan-12 10:53

I don't know how you showed it in the title bar?

This is my main window

hWnd = CreateWindow(
        sz_WindowClass,
        sz_Title,
        WS_OVERLAPPEDWINDOW | WS_CLIPCHILDREN | WS_EX_CONTROLPARENT,
        CW_USEDEFAULT, 0,
        CW_USEDEFAULT, 0,
        NULL,
        NULL,
        hInstance,
        NULL
     );

jkirkerx10-Jan-12 10:22

10-Jan-12 10:22

When I close my program in visual studio 2010 running in debug, I notice that I have to stop debug, to fully close the program. So I've been running my compiled exe's and the same thing happens, in which I have to use task Manager to kill the process. The windows close, but the process is still running.

So perhaps I'm missing something in my WndProc.

I have a WM_DESTROY, but I don't have a WM_CLOSE switch

case WM_DESTROY:
PostQuitMessage(0);

This is my File Exit

case IDM_FILE_EXIT:
PostMessage(hWnd, WM_CLOSE, 0, 0);
break;

Luc Pattyn10-Jan-12 10:24

Luc Pattyn

10-Jan-12 10:24

Do you have any extra threads running, that aren't marked "background threads"?

Smile | :)

Luc Pattyn [My Articles] Nil Volentibus Arduum

jkirkerx10-Jan-12 11:27

10-Jan-12 11:27

I'm not sure, but that's a good start or point in the right direction.

Eugen Podsypalnikov11-Jan-12 4:15

Eugen Podsypalnikov

11-Jan-12 4:15

Try "Break" instead of "Stop" for your debug session
and observe the stack(s) of the existing thread(s) Smile | :)

They sought it with thimbles, they sought it with care;
They pursued it with forks and hope;
They threatened its life with a railway-share;
They charmed it with smiles and soap. Smile | :)

jkirkerx11-Jan-12 6:33

11-Jan-12 6:33

That's a good idea

MSG m;
while(GetMessage(&m, NULL, 0, 0)) <-- Break
{
    if (!IsDialogMessage(hUserAccount_Index, &m))
    {
        TranslateMessage(&m);
        DispatchMessage(&m);
    }
}

Mohibur Rashid10-Jan-12 14:11

10-Jan-12 14:11

Dont post WM_CLOSE message post WM_DESTROY Message

or
Call the PostQuitMessage function under WM_CLOSE case.

Richard MacCutchan10-Jan-12 21:58

Richard MacCutchan

10-Jan-12 21:58

Posting the WM_CLOSE is quite correct.

Unrequited desire is character building. OriginalGriff
I'm sitting here giving you a standing ovation - Len Goodman

Mohibur Rashid10-Jan-12 22:09

10-Jan-12 22:09

I am not saying WM_CLOSE is wrong.

But I think OP did not call that function under WM_CLOSE message.

Richard MacCutchan10-Jan-12 22:48

Richard MacCutchan

10-Jan-12 22:48

The default action for WM_CLOSE[^] will do what's necessary.

Unrequited desire is character building. OriginalGriff
I'm sitting here giving you a standing ovation - Len Goodman

Mohibur Rashid10-Jan-12 23:01

10-Jan-12 23:01

Yes, I agree with you. I developed a small program to check the behavior of WM_CLOSE. And It does its job.

Anyway:

If you want to check how many thread is used by your program just open the task manager then click on menu View->Set Column and then choose thread check box, You will get the thread count

Richard MacCutchan10-Jan-12 23:11

Richard MacCutchan

10-Jan-12 23:11

johny10151981 wrote:
WM_CLOSE. And It does its job.

As I said.

johny10151981 wrote:
If you want to check how many thread is used by your program ...

Agreed, but it's not me who wants to know.

Unrequited desire is character building. OriginalGriff
I'm sitting here giving you a standing ovation - Len Goodman

Mohibur Rashid11-Jan-12 0:37

I need to get schooled on shutting down my program

11-Jan-12 0:37

My Bad It was not for you, It was for The OP.

jkirkerx11-Jan-12 8:14

Re: I need to get schooled on shutting down my program

11-Jan-12 8:14

I just came to that conclusion, that I did not handle my WndProc Correctly. So I started to remodel it with a better understanding. I must admit that I should check for open threads still running during one of the events.

I do need some help in organization and clarity here.

WM_CLOSE
Gives me a chance to do something before WM_DESTROY is called

WM_DESTROY
That's it, shutting down, I must do something, or it just shuts down

WM_QUIT
I'm suppose to PostQuitMessage(0), 0 means close, 1 means abort?

case IDM_FILE_EXIT:
PostMessage(hWnd, WM_CLOSE, 0, 0);
break;

case WM_CLOSE:
  {
    // Catch the Event and do something before shutting down
    msgboxID = MessageBoxEx(g_hWndMainFrame,
    L"Are you sure you wish to quite Internet Commerce Engine 5",
    L"Question",
    MB_OKCANCEL | MB_DEFBUTTON1 | MB_ICONINFORMATION,
    LANG_NEUTRAL
    );
  }

  switch ( msgboxID )
  {
      case IDOK:
      PostQuitMessage(0);
      DestroyWindow(hWnd);
      break;

      case IDCANCEL:
      PostQuitMessage(1);
      break;
  }
  break;

  case WM_DESTROY:
      // Perform Cleanup Tasks

      break;

  case WM_QUIT:

      PostQuitMessage(0);
      break;

Wes Aday11-Jan-12 8:21

Wes Aday

11-Jan-12 8:21

jkirkerx wrote:
PostQuitMessage(0), 0 means close, 1 means abort?

The parameter is an exit code that you want to return from your program. The numbers do not mean anything unless you, as the programmer, define a meaning for them.

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
Individuality is fine, as long as we do it together - F. Burns

Re: I need to get schooled on shutting down my program

jkirkerx11-Jan-12 8:34

Re: I need to get schooled on shutting down my program

11-Jan-12 8:34

Yah that didn't work. Think I'm closer now

case WM_CLOSE:
        {
            // Catch the Event and do something before shutting down
            msgboxID = MessageBoxEx(g_hWndMainFrame,
            L"Are you sure you wish to quite Internet Commerce Engine 5",
            L"Question",
            MB_OKCANCEL | MB_DEFBUTTON1 | MB_ICONINFORMATION,
            LANG_NEUTRAL
            );

            switch ( msgboxID )
            {
                case IDOK:
                    Sleep(1000);
                    PostQuitMessage(0);
                    return 0;
                    break;

                case IDCANCEL:
                    return 1;
                    break;
            }
        }
        break;

    case WM_DESTROY:
        // Perform Cleanup Tasks

        break;

    case WM_QUIT:
        DestroyWindow(hWnd);
        break;

Wes Aday11-Jan-12 8:39

Wes Aday

11-Jan-12 8:39

jkirkerx wrote:
case WM_QUIT:
DestroyWindow(hWnd);
break;

When the thread retrieves the WM_QUIT message from its message queue, it should exit its message loop and return control to the system.

Re: I need to get schooled on shutting down my program

jkirkerx11-Jan-12 9:17

I want the message loop in the mdi child window for the tab function

11-Jan-12 9:17

I need to fix my child window first. I think I have the main window fixed. I have the same loop in the parent window and child window, so the child window is still running the loop when I try to shutdown the main window.

Now I'm starting to think that I have to call DestroyWindow for each control as well.

Main Window

case WM_CLOSE:
        {
            // Catch the Event and do something before shutting down
            msgboxID = MessageBoxEx(g_hWndMainFrame,
            L"Are you sure you wish to quit Internet Commerce Engine 5",
            L"Question",
            MB_OKCANCEL | MB_DEFBUTTON1 | MB_ICONINFORMATION,
            LANG_NEUTRAL
            );

            switch ( msgboxID )
            {
                case IDOK:
                    Sleep(1000);
                    PostQuitMessage(0);

                    //return 0;
                    break;

                case IDCANCEL:
                    return 1;
                    break;
            }
        }
        break;

    case WM_DESTROY:
        DestroyWindow(hWnd);
        break;

    case WM_QUIT:

        break;

Child Window

case WM_CLOSE:			
{
	HMENU	hMenu;
	HMENU	hManagementMenu;
		
	hMenu = GetMenu( gUserAccount_Index_GAC );
	EnableMenuItem(hMenu, 1, MF_BYPOSITION | MF_ENABLED);            
	hManagementMenu = GetSubMenu(hMenu, 1);
	EnableMenuItem(hManagementMenu, IDM_MANAGEMENT, MF_BYCOMMAND | MF_ENABLED);
	DrawMenuBar( gUserAccount_Index_GAC );				
}

return 0;
break;
		
case WM_DESTROY:
{
	if ( hUserAccount_Index ) 
		hUserAccount_Index = NULL;

	DestroyWindow(lbl_UserAccount_Index_Label);
	DestroyWindow(lb_UserAccount_Index_Listbox_Field);
	DestroyWindow(bt_UserAccount_Index_Add);
	DestroyWindow(bt_UserAccount_Index_Edit);
	DestroyWindow(bt_UserAccount_Index_Delete);
	DestroyWindow(bt_UserAccount_Index_Exit);	
	DestroyWindow(cWnd);
	}
	return 0;
	break;

	case WM_QUIT:
					
	break;

jkirkerx11-Jan-12 14:17