Re: How to debug this? (MFC dialog control question.) - C / C++ / MFC Discussion Boards

Re: How to debug this? (MFC dialog control question.)

David Crow28-Aug-07 6:56

28-Aug-07 6:56

So if you set a breakpoint in the event handler and check the call stack, what do you see?

In any case, why is this a problem? Is it causing something to not get drawn?

"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: How to debug this? (MFC dialog control question.)

@largeinsd28-Aug-07 7:19

@largeinsd

28-Aug-07 7:19

Dave,

Thanks for your interest! It's a problem for the opposite reason, it IS causing something to be drawn. Basically, the rest of the dialog configuration depends on which radio button is selected... so when it automatically selects somethin', it's configuring the dialog according to that. And I'm trying to design it so that it comes up blank, ready for a radio button to be selected.

Here's the first entry in the call stack prior to the event handler:

>Direct3DMFC.exe!_AfxDispatchCmdMsg(CCmdTarget * pTarget=0x0012e460, unsigned >int nID=1062, int nCode=0, void (void)* pfn=0x00523fb6, void * >pExtra=0x00000000, unsigned int nSig=56, AFX_CMDHANDLERINFO * >pHandlerInfo=0x00000000) Line 82 C++

Any further suggestions? I should point out that in attempting to debug this little caper i have done the following:

1) Moved the radio button to another location (bug persists)
2) Deleted the message map according to this event handler (bug goes away)
3) Created another radio button with another name for handling similar events. (This one now takes the problem.)
4) Checked as many params etc as I can think of to see why this radio button would be different from all the others? The only thing that I can think of is that it may have been the last one that I put on there.

Yay - debugging!

Thanks again - Jason

Re: How to debug this? (MFC dialog control question.)

David Crow28-Aug-07 7:28

David Crow

28-Aug-07 7:28

@largeinsd wrote:
Basically, the rest of the dialog configuration depends on which radio button is selected... so when it automatically selects somethin', it's configuring the dialog according to that.

Do you have an int member variable that represents all the radio buttons, or do you have a CButton member variable for each?

"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: How to debug this? (MFC dialog control question.)

@largeinsd28-Aug-07 9:00

@largeinsd

28-Aug-07 9:00

DavidCrow wrote:
Do you have an int member variable that represents all the radio buttons, or do you have a CButton member variable for each?

The former - I have an int variable which is initialzed to -1 (no selection) in the constructor, and then when I get an "OnBnClickedRdBox1" event I do the following:

void CShapeSelect::OnBnClickedRdBox1()<br />
{<br />
	m_ShapeSelected = 2;<br />
	GetParent()->PostMessage(WM_SHAPE_RADIO_CHANGED);<br />
}

Re: How to debug this? (MFC dialog control question.)

David Crow28-Aug-07 9:06

David Crow

28-Aug-07 9:06

@largeinsd wrote:
The former - I have an int variable...

I would lose that and use a CButton for each. Far less confusing that way.

"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: How to debug this? (MFC dialog control question.)

@largeinsd28-Aug-07 9:54

@largeinsd

28-Aug-07 9:54

DavidCrow wrote:
I would lose that and use a CButton for each. Far less confusing that way.

Ok, well I'm gonna go ahead and implement that, if nothing else hoping to work around this problem.

But let me ask you this - is there a way to make the dialog class catch the button selection event that is slightly more elegant than they way i've done it here with my own call to PostMessage ?

Thanks - Jason

Re: How to debug this? (MFC dialog control question.)

David Crow28-Aug-07 10:40

David Crow

28-Aug-07 10:40

@largeinsd wrote:
But let me ask you this - is there a way to make the dialog class catch the button selection event that is slightly more elegant than they way i've done it here with my own call to PostMessage ?

Sure. Just use ClassWizard (Ctrl+W) to create a BN_CLICKED handler. All the buttons can use the same handler, or they can each have their own.

"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: How to debug this? (MFC dialog control question.)

@largeinsd28-Aug-07 10:40

@largeinsd

28-Aug-07 10:40

Ok, here's the update you're just dying to here:

i encounter the same problem using buttons - as soon as i add an event handler to take action when the radio buttons are selected, it gets activated on initialization. however, using method i can at least use the

m_MyRadioButton.GetChecked()

method to do some screening. it's a fine work around, but where is the ELEGANCE?

Re: How to debug this? (MFC dialog control question.)

David Crow28-Aug-07 10:44

David Crow

28-Aug-07 10:44

@largeinsd wrote:
...it gets activated on initialization.

The solution to this is to differentiate between initialization and the actual clicking of one of the buttons. I use a bool member variable to denote this.

"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: How to debug this? (MFC dialog control question.)

Reagan Conservative28-Aug-07 8:26

Reagan Conservative

28-Aug-07 8:26

Also, don't you need a Group Box for the radio buttons to act properly? Is that not true David?

John P.

Re: How to debug this? (MFC dialog control question.)

@largeinsd28-Aug-07 9:07

@largeinsd

28-Aug-07 9:07

jparken wrote:
Also, don't you need a Group Box for the radio buttons to act properly? Is that not true David?

Ok, interesting point. For what it's worth I do have the radio buttons enclosed in a group box. If there is some particular initialization required, please let me know.

-Jason

Re: How to debug this? (MFC dialog control question.)

David Crow28-Aug-07 10:42

David Crow

28-Aug-07 10:42

jparken wrote:
Also, don't you need a Group Box for the radio buttons to act properly? Is that not true David?

No, a group control (i.e., a control having the BS_GROUPBOX style) is not necessary. Perhaps you are confusing that with the first radio button of the group having the WS_GROUP style and all others in the group not.

"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

file creation failure

act_x28-Aug-07 6:13

act_x

28-Aug-07 6:13

I am trying to programatically create an empty file in a location such as

C:\Program Files\Common Files\myCo\MyTool\Temp.dat

However using the CFile member , I get a failure with code = 3

Is it not possible to create a file where the upper directories have not been created ?

This is the code I am using

<br />
<br />
		CFile f;<br />
		CFileException e;<br />
<br />
		if( !f.Open( m_strFileName, CFile::modeCreate /*| CFile::modeWrite*/, &e ) )<br />
		{<br />
#ifdef _DEBUG<br />
			afxDump << "File could not be opened " << e.m_cause << "\n";<br />
#endif		<br />
			// Log Failure <br />
		}<br />
		else<br />
		{<br />
                   // Log Success <br />
<br />
<br />
		}<br />

Help is apprecaite d!

Re: file creation failure

C^hris L^osinger28-Aug-07 6:23

C^hris L^osinger

28-Aug-07 6:23

act_x wrote:
Is it not possible to create a file where the upper directories have not been created ?

image processing toolkits | batch image processing

Re: file creation failure

Chris Meech28-Aug-07 6:47

Chris Meech

28-Aug-07 6:47

You might make use of this function.

<br />
bool MakeSureDirectoryPathExists(PCSTR strPath);<br />

It helps when you are unsure of whether the entire path exists or not before you open a file.

Chris Meech
I am Canadian. [heard in a local bar]

Re: file creation failure

David Crow28-Aug-07 6:54

David Crow

28-Aug-07 6:54

Call SHCreateDirectoryEx() before creating the file.

"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

OnLButtonDown and Up

mcsherry28-Aug-07 6:05

mcsherry

28-Aug-07 6:05

On a dialog based application I have attached an OpenGL window which is overlaid on a static control. When the user does a left mouse button down followed by a left mouse button up on the opengl window I want an event to occur. However i have the following constraints:
If the user leaves the area of the opengl window and release the left mouse button i don't want the event to happen
If they then press the left mouse button down outside of the opengl model and then release it whilst in the opengl window i don't want the event to happen.

However if they press the left mouse button inside the opengl window, then leave the opengl window but then come back into it and then release the mouse button the event should happen

I've tried using the left button down event on the main dialog however if the user clicks (down or up) on any of the other buttons on the dialog then the main dialog doesn't handle the event.

Does anyone know how to handle this set of events (or even what I'm talking about? Big Grin | :-D

)?

TIA,
Andy

Re: OnLButtonDown and Up

Mark Salsbery28-Aug-07 6:21

Mark Salsbery

28-Aug-07 6:21

This is an MFC example, but if you're using straight APIs you can do the same.
::MessageBeep() should get called on the left button up message according
to your requirements (unless I need more caffeine)...

void CMyWindow::OnLButtonDown(UINT nFlags, CPoint point)
{
    CWnd::OnLButtonDown(nFlags, point);

    SetCapture();
    fInCapture = true;
}

void CMyWindow::OnLButtonUp(UINT nFlags, CPoint point)
{
    if (fInCapture)
    {
        ReleaseCapture();
        fInCapture = false;

        CRect clirect;
        GetClientRect(&clirect);
        if (PtInRect(&clirect, point))
        {
            //** test
            ::MessageBeep(-1);
            //** end test
        }
    }

    CWnd::OnLButtonUp(nFlags, point);
}

Mark

Mark Salsbery
Microsoft MVP - Visual C++
Java | [Coffee]

Re: OnLButtonDown and Up

mcsherry28-Aug-07 6:47

mcsherry

28-Aug-07 6:47

cheers Mark, worked a treat

CMenu problem

prithaa28-Aug-07 5:19

prithaa

28-Aug-07 5:19

Hello,

I have a class derived from CMDIChildWnd .In one of the functions I have written

CMenu p;
GetParentFrame()->SetMenu(&p);
But the menu doesn't change.
What else I need to do to change the menu?

Regards
Prithaa

Re: CMenu problem

Iain Clarke, Warrior Programmer28-Aug-07 5:26

Iain Clarke, Warrior Programmer

28-Aug-07 5:26