Yes, they perfectly work togheter ... swend me an email, and I'll send to you a test application ...

Very interesting, but I think you should direct your comments to the OP. Just say 'NO' to evaluated arguments for diadic functions! Ash

Please start providing some clear facts about your tools, their switch settings, your app, the kind of calculations you are doing, what parts run fine, what parts don't, how the results are different from what you want; show us a code sample (with variable declaration!) and some relevant results (twice: good and bad). i.e. stop saying "it doesn't work" :) Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles] Nil Volentibus Arduum Please use <PRE> tags for code snippets, they preserve indentation, and improve readability.

Check for overflow. If doing a long string of computations, break them up; you may have precedence wrong.

you're welcome. :) Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles] Nil Volentibus Arduum Please use <PRE> tags for code snippets, they preserve indentation, and improve readability.

There aren't any CDialog type windows, and 'this' is just some abstract class where I have the time-stepping loop. Another thing I tried: Even though it's a dll, I tried adding a form to it, and dragged a progressbar on it, but then didn't quite know how to invoke this form from my abstract class. I'll look up the message loop idea. Thanks for the input. sb

I suspect it's because free() and malloc() are already defined in libc.lib... ;P [VisualCalc][Binary Guide][CommDialogs] | [Forums Guidelines]

Hi Suman, The fortran modules are just .for text files that reside in the project. They aren't compiled separately and linked. If I make a win32 console app and include these .for files as source files, the app compiles, links and runs fine. I have Visual Fortran on the machine and Visual Studio seem to know what to do in the case of a win32 app. But for an MFC app, it gives linker errors. I dont have a separate fortran project. thanks, sb

That was the problem, Mark. I had built debug dlls. Soon as I changed the project configuration I was able to load the librar. MAny thanks! sb

ns wrote: What is it I need to do? You need to configure your project to include any dependent header files and resolve any dependent library files to successfully compile and link.

ns wrote: Do I need to include something? Yes, read here (near the bottom) for what. "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

Thanks Cedric, It wanted _AFXDLL after I unchecked the inherited ones, so I entered it by hand. It seems to have gotten past that point now. Apppreciate your help, sb

ns wrote: What is the aps file you mention? I think it is an APp Studio file. ns wrote: ...is there an aps file? Yes, there very well could be. "Approved Workmen Are Not Ashamed" - 2 Timothy 2:15 "Judge not by the eye but by the heart." - Native American Proverb

modeless? GetDesktopWindow() Kuphryn

You should make that dialog part of your app, instead of an addition. This way, your app will be cleaner and more robust. That being said, if you insist, you could keep the dialog alive after you terminate the app. Follow these steps: 1) Write another little app2, which handles the dialog. 2) Spawn app2 from within app. 3) Terminate app. This will no doubt create unnecessary complexities to your application. - It's easier to make than to correct a mistake.

What the others have said, and also, if you want ClassWizard to work correctly, you need to make all this stuff match ... // ClassWizard generated virtual function overrides //{{AFX_VIRTUAL(CGraphCtrl) should be // ClassWizard generated virtual function overrides //{{AFX_VIRTUAL(CScale) Be careful what you cut and paste - don't forget the edit! I've seen better runs in my shorts! - Patches O'Houlihan

Here is what worked for me: CClientDC dc(this); CFont l_font; l_font.CreateFont(14, 0, 0, 0, FW_NORMAL, FALSE, FALSE, FALSE, 0, OUT_DEFAULT_PRECIS, CLIP_DEFAULT_PRECIS, DEFAULT_QUALITY, DEFAULT_PITCH | FF_ROMAN, "Times New Roman"); CFont* l_old_font = dc.SelectObject(&l_font); dc.TextOut(50, 50, "Hello World"); dc.SelectObject(l_old_font); // Delete the font object. l_font.DeleteObject(); except that I got my CDC in the OnraseBackground function of the CStatic class. Thanks everyone for helping. sb

Michael Dunn wrote: Those calls to GetDC() are bad - you need to release every DC you get. You are right -- explicit releasing should be preferable. Actually MFC is able to release various handles at idle time. Values returned by GetDC and other functions are temporary objects which are stored in a collection. They a released between message processing.

you can use WM_PAINT instead WM_ERASEBKGND void CAnswer::OnPaint() { CPaintDC dc(this); dc.SetBkMode(0); dc.TextOut(50,42,"aaaa",30); }_** **_ whitesky

Cedric Moonen wrote: just 'ask' for a repaint, that will erase everything We all know what you meant but what you typed is a different story ;) I'm just reading it from the thread issuer's view and if they take you literally, they'll just call Invalidate() in their button pressed handler which will ultimately generate the call to the OnDraw which drew the graph in the first place effectively redrawing it once again. I'm guessing what you meant to say was in the button pressed handler, set some member variable to false like... // declaration BOOL m_bDrawGraph; // constuctor m_bDrawGraph=TRUE; // On button pressed handler m_bDrawGraph=FALSE; Invalidate(); // OnDraw if (m_bDrawGraph) { // Draw the graph, etc... } else { // OnEraseBackground already cleared the background // but you are free to draw something else here etc... } /* Don't forget that what goes up, must come down. Make sure to provide some mechanism, such as another button and another handler to set the m_bDrawGraph=TRUE when you want to see the graph again. Don't forget to Invalidate() to force a redraw. IMPORTANT: Remember that OnDraw gets called frequently, even when you did not explicitly call Invalidate(). OnDraw needs to know what to draw in your client area at any moment when someone drags another window over your window which effectively wipes out part of the graph so Windows politely Invalidates for you to "redraw" the graph. */ Anyway, I apologize for the clarification but I hope it helps a little.