C / C++ / MFC

9-Feb-09 20:17

Check this![^]

-Sarath.
"Great hopes make everything great possible" - Benjamin Franklin

My blog - Sharing My Thoughts

Re: ReportView Style

SandipG 9-Feb-09 20:18

Custom Message From Child Dialog

9-Feb-09 20:18

Check this article Q 4.01
45 Day Series: CodeProject VC++ Forum Q&A - I[^]
I hope it helps.

Regards,
Sandip.

Re: ReportView Style

ATM@CodeProject9-Feb-09 21:44

ATM@CodeProject

9-Feb-09 21:44

Thanks for the reply can i set the color of text ?..

zakkas24839-Feb-09 19:25

9-Feb-09 19:25

Hello every one,

I have child - parent dialog in my application. I wants to call parent class function from child class. using WM_USER. please provide me the example code. i have already code this but having problem in realse exe.

Thank you.

_AnsHUMAN_ 9-Feb-09 19:34

_AnsHUMAN_

9-Feb-09 19:34

zakkas2483 wrote:
. i have already code this but having problem in realse exe.

What problem? How do you implement it.

You need to google first, if you have "It's urgent please" mentioned in your question.
Wink | ;-)

_AnShUmAn_

zakkas24839-Feb-09 19:53

9-Feb-09 19:53

I have Two Dialog box. Abc and Def ok. From Add button of Abc i have created Def Dialog box. I need to do some work in Abc on OK of Def.

CODE:
// Abc.cpp
#define USER_MSG WM_USER + 100

BEGIN_MESSAGE_MAP(Abc, CDialog)
//{{AFX_MSG_MAP(Abc)
ON_MESSAGE( USER_MSG, DoSomeWork )
//}}AFX_MSG_MAP
END_MESSAGE_MAP()

void Abc::OnAdd()
{
Def d;
d.ptrParent = this;
d.DoModel();
}

void Abc::DoSomeWork()
{

}

/// From def.cpp
void def::OnOK()
{
if( ptrParent )
::sendMessage( ptrParent->m_hWnd, WM_USER + 100,0,0);
// i can do like ptrParent->DoSomeWork() but i wants to user USER MSG.
}

Thank you for your interest.

SandipG 9-Feb-09 20:09

9-Feb-09 20:09

Why you need messages for this purpose??
You can simply do something like this..

void Abc::OnAdd()
{
  Def d;
  d.ptrParent = this;
  if(d.DoModel()==IDOK)
  {
      ...
     // here you can acess data members of the class def using d directly..
  }
  else
  {
    ... 
  }
}

I hope it helps..
BTW: Plese use code block button below posting area for posting code snippets.

Regards,
Sandip.

zakkas24839-Feb-09 20:18

9-Feb-09 20:18

HI Sandip,
U r very right.
i wants learn metod of sending USER message.
Also i don't have member veriables for Def Dialog box. I am using GetDlgItem()

Thanks.

SandipG 9-Feb-09 20:32

9-Feb-09 20:32

zakkas2483 wrote:
Also i don't have member veriables for Def Dialog box. I am using GetDlgItem()

I have no idea how you are doing this..
Anyways if you want to learn user defined messages
check following articles.
How to send a user-defined message with SendMessage, PostMessage or PostThreadMessage[^]
and HOWTO: MFC user defined message maps[^]
I will suggest to use RegisterWindowMessage instead of WM_USER. There reasons why you should avoid using WM_USER you can just google to read more on it.
I hope it helps.

Regards,
Sandip.

Sarath C9-Feb-09 20:17

9-Feb-09 20:17

~~If your child dialog is modal dialog, then the message processing of parent wil be blocked~~. Better passing parent window pointer to child dialog and call the desired function.

Check this to know how to create user defined messages[^]

-Sarath.
"Great hopes make everything great possible" - Benjamin Franklin

My blog - Sharing My Thoughts

zakkas24839-Feb-09 20:44

9-Feb-09 20:44

Thank you Sarath,

I have createed my child dialog as model dialog. And child dialog able to send message to parent dialog in debug mode but it is not working with Release EXE... Why it is so?

SandipG 9-Feb-09 21:13

9-Feb-09 21:13

zakkas2483 wrote:
but it is not working with Release EXE... Why it is so?

Because you are not handling the WPARAM and LPARAM.
Even if you do not wish to use them you have to handle them.
Modify
DoSoemthing()
to
DoSomething(WPARAM wParam, LPARAM lParam)

I hope it helps.

Regards,
Sandip.

zakkas24839-Feb-09 21:36

9-Feb-09 21:36

Yes,

It's working...
After modify the defination of DoSomething( ) to DoSomething(WPARAM wParam, LPARAM lParam)
It's working find.
Thanks a lot for your kind support.
But i am not getting this think why it is working in debug mode and not with release mode. anyways thank a lot budy.. i am thankful to you.

Sarath C9-Feb-09 21:19

9-Feb-09 21:19

Can u post code snippet for the same?

-Sarath.
"Great hopes make everything great possible" - Benjamin Franklin

My blog - Sharing My Thoughts

zakkas24839-Feb-09 21:30

9-Feb-09 21:30

two File ..
one

//PostDialog.cpp

#define WM_UPDATE_SERVER_LIST WM_USER + 1
BEGIN_MESSAGE_MAP(CPortsDialog, CDialog)
//{{AFX_MSG_MAP(CPortsDialog)
ON_MESSAGE( WM_UPDATE_SERVER_LIST, UpdateServerList )
//}}AFX_MSG_MAP
END_MESSAGE_MAP()

void CPortsDialog::UpdateServerList( )
{
//do some work
}
/// function to create new dialog...
void CPortsDialog::OnButtonAdd()
{
CAddSMTPServer SMTPServer;
SMTPServer.ptrPortDialog = this;
SMTPServer.DoModal();
}

///AddSMTPServer.cpp

void CAddSMTPServer::OnOK()
{
if( ptrPortDialog ) // where ptrPortDialog is pointer to parent dialog
::SendMessage( ptrPortDialog->m_hWnd,WM_UPDATE_SERVER_LIST, 0,0);
//alternative
// ptrPortDialog->UpdateServerList( )

}

zakkas24839-Feb-09 21:39

9-Feb-09 21:39

After modify the UpdateServerList( ) function to UpdateServerList(WPARAM, LPARAM ) it's working fine.
But i am not getting why the previouse funcation defination work in debug mode and not work for release mode.. any idea. Anyway thank you very much for nice support. Wink | ;)

Sarath C9-Feb-09 23:21

9-Feb-09 23:21

The message handlers should have to format afx_msg LRESULT (CWnd::*)(WPARAM, LPARAM).
which means the void CPortsDialog::UpdateServerList( )

should be changed to LRESULT CPortsDialog::UpdateServerList(WPARAM, LPARAM)

-Sarath.
"Great hopes make everything great possible" - Benjamin Franklin

My blog - Sharing My Thoughts

Iain Clarke, Warrior Programmer

Iain Clarke, Warrior Programmer9-Feb-09 22:12

9-Feb-09 22:12

You already have the solution to your problem - add in the WPARAM & LPARAM parameters.

But you want to know why it worked in debug, and not in release mode?

Do a search in the MFC code directorys for ON_MESSAGE, and you can see the definition of the macro. You can see that MFC is calling casting your function to a format that includes the two parameters.

In release mode, calling a function with parameters will put those parameters on the stack. Your function does not use them, so it does not pull them off the stack. I got "stack corruption" errors when I had this same fault (a long time ago now!)

In debug mode, my theory there is plenty of padded memory about, or the calling conventions do not use the stack. Either way - when it worked in debug mode, you were just lucky.

(Or unlucky - I'd prefer to fix the problem as soon as possible!)

My experience was with VC++ 6 - I think later versions of MFC do things a little differently, without casts in the ON_xxxxx message maps, so it's harder to have this fault.

Iain.

Codeproject MVP for C++, I can't believe it's for my lounge posts...

zakkas24839-Feb-09 23:24