I gave up on windiff. We swapped to Winmerge on my last project, it's is a hell of a lot simpler to use and to get started with, plus the interface makes much more sense. [Edit: Fixed Link] Winmerge on Sourceforge If you can keep you head when all about you Are losing theirs and blaming it on you; If you can dream - and not make dreams your master; If you can think - and not make thoughts your aim; Yours is the Earth and everything that's in it. Rudyard Kipling

You're right, my mistake.:(

I just posted an answer using MFC, but these functions are just wrappers for the api's that you should be able to get with C++. I don't know the exact syntax, but it shouldn't be too dissimilar. Sorry I don't know more:( If it's broken, I probably did it bdiamond

Well, I have it working now but I'm still not sure exactly what is going on. This much I can say. The variable "hwnd" within DialogProc only exists when in the DialogProc routine. So, I created another variable called global_hdlg which I set to hdlg every time DialogProc is called. The other thread then declares global_hdlg as extern and passes it into SetDlgItemText. There must be a cleaner way to do this? Robert

Mr. Prakash, Thanks, I found a similar answer in another thread, from another Indian guy :) In the resource editor if you click in the middle of the combo box, blue squares appear on the left and right, allowing you to make the box wider or narrower. But, if you click on the pulldown itself, there is a single blue box in the bottom center. Grabbing that blue box and pulling it down defines what size the combo box is when initially displayed. Too bad they don't say anything about this in the help area... Actually, it is explained. It is under "Combo Boxes" then "sizing". Robert

Antony, Thanks for the tip. I switched the call to PostThreadMessage and in my thread I now periodically check for message arrival with PeekMessage and am seeing them there. Robert

This was the problem. I had the following code commented out: //wc.hbrBackground = GetStockObject(WHITE_BRUSH); I believe I did this because it didn't compile. I had to add a cast to it: wc.hbrBackground = (HBRUSH)GetStockObject(WHITE_BRUSH); The code was originally from some sample code. Figures it wouldn't compile... // Register the main window class. wc.style = CS\_HREDRAW | CS\_VREDRAW; wc.lpfnWndProc = (WNDPROC) MainWndProc; wc.cbClsExtra = 0; wc.cbWndExtra = 0; wc.hInstance = hinstance; wc.hIcon = LoadIcon(NULL, IDI\_APPLICATION); wc.hCursor = LoadCursor(NULL, IDC\_ARROW); wc.hbrBackground = GetStockObject(WHITE\_BRUSH); wc.lpszMenuName = "MainMenu"; wc.lpszClassName = "MainWindowClass"; Thanks Maksim, Robert

are you able to get the sys or cpu temperature? /\ |_ E X E GG

So what happens first, fopen() or fprintf()? A rich person is not the one who has the most, but the one that needs the least.

Just wanted to let you all know that I figured out the problem in case someone comes upon this thread in the future. The problem that I was having is that my declaration: CSerialWnd serial; Was located in the InitDialogProc routine which would get called from the main dialog processing routine upon receipt of the WM_INITDIALOG notification. I moved that declaration to be global and I started receiving serial notifications in the main dialog processing routine. Now I will be able to write the code that handles the serial data stream. Good Luck, Robert

Here's two options: 1) Qualify FILETIME as being in the global namespace as: ::FILETIME, so that the compiler knows you are not refering to the one in System::Runtime::InteropServices. 2) Instead of importing the entire InteropServices namespace, either qualify them explicitly, or just include the classes that you actually need (e.g. using System::Runtime::InteropServices::Blah). Dave http://www.cloudsofheaven.org

Sorry, CP = Code Project (those of us who live here tend to abbreviate).. The 'debug section' probably has some more ideas for you Robert, try http://www.codeproject.com/debug[^] where you'd find other gems like http://www.codeproject.com/debug/ctracerst.asp[^] and over in tools there's things like http://www.codeproject.com/tools/ss_log.asp[^] ... you just have to hunt around a bit ...