bloodwinner wrote: (solved)it turns out the last digit was a remaining one, for example,2228 is the real number recorded this time and I guess the more appropriate open mode for writing a file is "w+" ... :) Luc Pattyn try { [Search CP Articles] [Search CP Forums] [Forum Guidelines] [My Articles] } catch { [Google] }

An alternative way is to use the select() call (only if you use linux/unix platform). select will wait for a file descriptor to become active and read the data from this file descriptor. I assume you can establish a pipe interface with STDIN and then use select to monitor your fd. you can put select in a while loop to monitor the fds continuously and maybe fork() this function if you want control back...

bloodwinner wrote: I am using C Then you can't be using .NET and you're in the wrong forum. Try the visual C++ forum. Christian Graus - Microsoft MVP - C++ "I am working on a project that will convert a FORTRAN code to corresponding C++ code.I am not aware of FORTRAN syntax" ( spotted in the C++/CLI forum )

Sorry - Im was wrong - the fact that it works in foreground i missed. Ignore my posting. I thought you had a code design issue. Well, other guy suggested the os. I would say the same. And i think it is something you'll find in Linux articles. I don't know C threads and linux in the detail you might need.

This is the C++/CLI forum. .NET threads are much easier, if you're using C++/CLI, use those. Otherwise, try the Visual C++ forum. Christian Graus - Microsoft MVP - C++ "I am working on a project that will convert a FORTRAN code to corresponding C++ code.I am not aware of FORTRAN syntax" ( spotted in the C++/CLI forum )

Don't cross post and this subject is covered in several articles here on CodeProject. Do some work. led mike

This has nothing to do with "managed" development and you cross posted it into 3 forums and that subject is covered in several articles here on CodeProject. So to sum up.... stop posting garbage and do some work. led mike

Don't cross post and don't double post the same question. led mike

I have the same problem long time ago. It is a mix mode of string vs char. Here the solution: define string strd1 = "9"; as char strd1 [1]="9"; or CString strd1 ="9";

Use getline. And, next time, ask in the right forum :-) This is the C++/CLI forum. Christian Graus - Microsoft MVP - C++ Metal Musings - Rex and my new metal blog

bloodwinner wrote: http://www.codeproject.com/cpp/miniexcel.asp That article is not really "about" Excel Automation. You need to research the Microsoft Office Object Model specifically the Excel Object Model. The MSDN site has examples and of course the documentation to these COM interfaces. If you posted this in the correct forum it means you are using the .NET runtime for your project. In that case you can use the Microsoft supplied .NET libraries. http://support.microsoft.com/kb/302084[^] led mike

bloodwinner wrote: I am using the MFC dialog application. Then you're not using C++/CLI, are you ? bloodwinner wrote: dlg.m_sum=dlg.m_add1+dlg.m_add2 I assume you have associated ints with the text boxes, not edit controls ? Then you need to call UpdateData before you do the calculation, to bring down the variables, and UpdateData(FALSE) after the calculation, to populate the controls again. Or, maybe the other way around. Please ask in the right forum next time :-) Christian Graus - Microsoft MVP - C++ Metal Musings - Rex and my new metal blog

And if they are int you can use of SetDlgItemInt WhiteSky

Me too I wrote a program with SaveDC and RestoreDC:) _** **_ WhiteSky

bloodwinner wrote: do you mean both these two ways are ok? Sure. Otherwise, why would both exist? "Approved Workmen Are Not Ashamed" - 2 Timothy 2:15 "Judge not by the eye but by the heart." - Native American Proverb

See here[^] _** **_ WhiteSky

sure you include but i cant see header file in previous your thread i saw only #include:) anyway these erros are only a thing a include:) _** **_ WhiteSky

Because when Windows wants to repaint a window, because an obscured part was exposed or for another reason, it sends a WM_PAINT message to the window to get it to repaint itself. If you put the rendering code elsewhere you'll see the rendering but when a part of the window is obscured and then exposed (or for some other reason needs to be re-rendered) the WM_PAINT handler will regenerate the image but it will not include the line. Aside from this I suspect the WM_CREATE handler is too early anyway. This situation is set to change with Vista's DWM but still the WM_PAINT handler will remain the correct place to perform most rendering operations. Steve

See static Methods and Variables [^] and here[^] _** **_ WhiteSky