C / C++ / MFC

12-Dec-02 5:23

Hello everybody:
Everytime that I call the function CFileDialog::DoModal I'm getting an Assert error. This is what I have in my code:

<br />
        if (lastFileOpenPath.GetLength() > 0)<br />
	{<br />
		openDlg.m_ofn.lpstrInitialDir = lastFileOpenPath;<br />
	}<br />
<br />
	int nResult = openDlg.DoModal();

Is there something that I'm missing? Is any of you guys had this problem before? Any answer is more than welcome.

Have a good day!!!

Luis E. Cuadrado
Blush | :O

)

retZ12-Dec-02 5:43

12-Dec-02 5:43

are u sure it is getting into the if loop..if so, is lastFileOpenPath pointing to a existing directory on the machine ??

There are no failures; there are only extended learning opportunities.

Luis E. Cuadrado12-Dec-02 6:15

12-Dec-02 6:15

By the if...loop you mean the following?

if (lastFileOpenPath.GetLength() > 0)
{
openDlg.m_ofn.lpstrInitialDir = lastFileOpenPath;
}

If so, yes. I did a step over and I was able to see it being executed. After it comes out of the if then the DoModal function throws and assert error.

About lastFileOpenPath, yes is pointing to a directory in the machine. I'm able to open the file selected by the open file dialog. But I have to click Ignore when I get the assert error.

Thanks,

Luis E. Cuadrado
Blush | :O

)

retZ12-Dec-02 7:04

12-Dec-02 7:04

wait a minute ! u r assigning a CString to a LPCTSTR (openDlg.m_ofn.lpstrInitialDir = lastFileOpenPath)..i guess u have to do a casting to do that ??

There are no failures; there are only extended learning opportunities.

Ravi Bhavnani12-Dec-02 6:51

Ravi Bhavnani

12-Dec-02 6:51

What is it ASSERTing on?

/ravi

Let's put "civil" back in "civilization"
http://www.ravib.com
ravib@ravib.com

Luis E. Cuadrado12-Dec-02 7:16

12-Dec-02 7:16

It is ASSERTing in the DoModal function in the DLGFILE.CPP. The ASSERT comes out after selecting a file from the Open Dialog.

This is where is ASSERTing on in the DLGFILE.CPP:

if (nResult)
ASSERT(pThreadState->m_pAlternateWndInit == NULL); <-- HERE
pThreadState->m_pAlternateWndInit = NULL;

when I check the Developer Studio's call stack, it's comming from here:

if (lastFileOpenPath.GetLength() > 0)<br />
	 {<br />
		openDlg.m_ofn.lpstrInitialDir = lastFileOpenPath;<br />
	 }

int nResult = openDlg.DoModal(); <--- HERE

I hope this helps.

Thanks,

Luis E. Cuadrado
Blush | :O

)

Ravi Bhavnani12-Dec-02 7:23

Ravi Bhavnani

12-Dec-02 7:23

This is probably a dumb request, but can you post the declaration of the openDlg variable?

/ravi

Let's put "civil" back in "civilization"
http://www.ravib.com
ravib@ravib.com

Luis E. Cuadrado12-Dec-02 7:28

12-Dec-02 7:28

No problem. This is pretty much how the source file looks like:

CFileDialog openDlg;<br />
.<br />
.<br />
.<br />
if (lastFileOpenPath.GetLength() > 0)<br />
{<br />
	openDlg.m_ofn.lpstrInitialDir = (LPCTSTR)lastFileOpenPath;<br />
}<br />
int nResult = openDlg.DoModal();

Thanks,

Luis E. Cuadrado
Blush | :O

)

Alvaro Mendez12-Dec-02 8:12

12-Dec-02 8:12

I'm not familiar with the code that's failing the assertion but I read through it a bit and it seems like pThreadState->m_pAlternateWndInit is not NULL whenever the OFN_EXPLORER flag is set in the m_ofn member. Are you setting that flag yourself, by any chance? If so, try not setting it and see if it makes a difference.

Regards,
Alvaro

Well done is better than well said. -- Benjamin Franklin
(I actually prefer medium-well.)

Luis E. Cuadrado12-Dec-02 9:16

12-Dec-02 9:16

I checked and I found out that the person that wrote the code, was setting the OFN_EXPLORER tag. I commented that part out and it doesn't make a diference. It still fails the assertion.

Thanks for your help!!
Best regards,

Luis E. Cuadrado
Blush | :O

)

Alvaro Mendez12-Dec-02 9:30

Win2K not drawing rectangle

12-Dec-02 9:30

OK, here's one last stab at this issue.

Is the dialog box being created in a separate thread? If so, is it using a parent window which was created in a different thread? This may be the problem. MFC does not support related windows being created accross different threads -- I forgot exactly why, but someone here may shed some light.

Regards,
Alvaro

Well done is better than well said. -- Benjamin Franklin
(I actually prefer medium-well.)

Shay Harel12-Dec-02 4:17

Shay Harel

12-Dec-02 4:17

Hi All !

I have this piece of code working fine on NT but drwas nothing on Windows 2000, any idea. Basically, it draws a rectangle on a dialog.

<br />
CClientDC dc (dlg);	//get our device context<br />
dlg->GetClientRect (&rect);		//get the pointer to our window<br />
CBrush brush (RGB (192,192,192));<br />
dc.SelectObject(&brush);<br />
					<br />
dc.Rectangle(x_base+(d*20),y_base+(c*30),x_base+20+(<br />

retZ12-Dec-02 4:37

12-Dec-02 4:37

i just ran that piece of code on Win2k and works fine..i tested with coordinates (0,0,100,100)..
just check ur co-ordinates ie [dc.Rectangle(x_base+(d*20),y_base+(c*30),x_base+20+(]

may the co-ordinates are just not "inside" the dialog..

There are no failures; there are only extended learning opportunities.

Shay Harel12-Dec-02 4:46

Shay Harel

12-Dec-02 4:46

They are inside because when I run the same code on NT, I see them, so this is funny...

Thank you anyways !

retZ12-Dec-02 5:17

12-Dec-02 5:17

wait a minute ! hope i am not confusing u here..its been a long time since i had worked on such stuff..
could it be due to screen resolution..because of things like screen co-ordinates or client co-ordinates..ohhhh i am so forgetful...

There are no failures; there are only extended learning opportunities.

Window not updating entirely

generic_user_id12-Dec-02 5:54

generic_user_id

12-Dec-02 5:54

In that case using ScreenToClient() should solve it.

Regards,

Griffith

Everything you say will be misquoted, ripped out of context and used against you.

jimNLX12-Dec-02 3:30

jimNLX

12-Dec-02 3:30

I wrote this dialog app and after it runs for awhile it just stops updating all the objects on the screen. What I mean by not updating is that some of the object just stop appearing or are only drawn partially. I have many pages in this dialog and they mostly just have large buttons on them. I'm not calling wm_paint or messing with any of the draw functions, I have just let Windows handle that.

Also, I noticed that some of the drop downs instead of having a down arrow it will display a "6".

Any idea on how I can make sure that everything gets drawn on the screen?

retZ12-Dec-02 4:43

12-Dec-02 4:43

i am not really sure of the answer..just a guess..
Could you check if ur app is leaking memory..could u check the taskmanager to see ur app's mem utilization ?

There are no failures; there are only extended learning opportunities.

valikac12-Dec-02 8:01

valikac

12-Dec-02 8:01

Make sure that the application is not storing huge amount of data in memory and continue adding more data. The program could have memory leaks.

Check task manager and make sure the size of the process in more is consistant and does not increase dramatically.

Kuphryn

Alvaro Mendez12-Dec-02 8:24

12-Dec-02 8:24

It looks to me like a resource leak, but you say you're not using the GDI functions. Are you sure about this? Maybe it's not your code but someone else could have added drawing functionality in there you don't know about.

Another idea that comes to mind is if your app opens and closes the dialog but does not properly destroy it whenever it gets closed. In other words, it may look like it's gone, but it remains hidden and the resources are not released.

That's all I can offer. Good luck!

Regards,
Alvaro

Well done is better than well said. -- Benjamin Franklin
(I actually prefer medium-well.)

jimNLX12-Dec-02 8:29

jimNLX

12-Dec-02 8:29

These all sound like good suggestions. I have been running some test to see if memory changes significantly, but haven't seen this happen.

On all of the dialogs that are called I do a delete() when I close them. I've check and every page is done this way.

Is a particular area I can look at in the debugger to see what is going on?

Thanks...

Alvaro Mendez12-Dec-02 9:36