Just reorg your directories and put arrange the files that way. The only implementation I put in header files is 1-line returns and/or single "set" functions. At least I'm not as bad as some people I know, they have a seperate cpp file for every function in the header! My rule is, break out another cpp if your function is 30-ish lines or longer, just for clarity. (although there should be very few cases where you need such a big function) ~Nitron. ññòòïðïðB A start

doneirik wrote: Could anyone tell me how to cope with this error message. the start of my code goes like #pragma once using namespace std; ... I get the errormessage that the namespace does not exist, and msdn provide little information about this error message. error C2871: ´std´:a namespace with this name does not exist You probably should include a file with code in namespace std before 'using' namespace std, e.g. #include <vector> using namespace std;

For your MessageBox problem... In stdafx.h just add #undef MessageBoxA or MessageBox don't remember. To close your dialog take a look at this and I'm going to help you a bit... // Set the accept button of the form to button1. form1->AcceptButton = button1;

doneirik wrote: I want the messagebox to close when I press the "OK" button All messageboxes are like that... Call CDialog::OnOK(); on the click event of your OK Button.. Ninety-eight percent of the thrill comes from knowing that the thing you designed works, and works almost the way you expected it would. If that happens, part of you is in that machine.

The Windows headers declare two versions of most APIs that take string parameters or buffers which contain strings. These typically end in either W, for a version taking Unicode (word-oriented) strings, or A, for a version taking ANSI (byte-oriented) strings. Windows 9x, in the main, only supplies the ANSI versions; Windows NT and successors (2000, XP, 2003) supply both versions. So there are actually two functions in the API: MessageBoxA and MessageBoxW. For convenience the headers define a macro which, depending on whether UNICODE is defined, maps to the W or A version of the API. This allows Unicode and ANSI versions of the software to be compiled from the same sources just by defining or not defining UNICODE. So MessageBox is a macro defined to either MessageBoxW or MessageBoxA - the former if UNICODE is defined and the latter if not. The C++ macro processor is dumb. It doesn't understand that you're trying to call the Windows Forms MessageBox class's Show method. It just replaces the text with either MessageBoxW or MessageBoxA. This will give a compile error because there's no class with that name. I think the best thing for you to do is to isolate the .NET code in one set of source files, and the unmanaged code in another set. In the unmanaged set, include windows.h; in the managed files, don't. If it's in your precompiled header file, remove it. Stability. What an interesting concept. -- Chris Maunder

MessageBoxA is the ANSI version of MessageBox (MessageBox is actually a macro that expands to MessageBoxA in ANSI builds and MessageBoxW in UNICODE builds). Apparently the compiler can't see the definition of MessageBoxA at the point of error. Perhaps you didn't include the correct header files in the correct order, or you may have unmatched #ifdef/#endif statements. Since it happens when you include your own header file I'd look in that for unmatched statements. Disclaimer: I have never worked in VC++.net 2003, but the above applies to VC++ 6.0. Cheers Steen. "To claim that computer games influence children is ridiculous. If Pacman had influenced children born in the 80'ies we would see a lot of youngsters running around in dark rooms eating pills while listening to monotonous music"

Yea, I got the same.... Use the file name if you can. That works no problem. picBox->Image = Image::FromFile(S"filePic.bmp")

the best one i've seen so far is the 'EasySize' article here on CP My articles www.stillwaterexpress.com BlackDice

See here. "Opinions are neither right nor wrong. I cannot change your opinion. I can, however, change what influences your opinion." - David Crow

Something like: void function( char arr[] ) { } void main( void ) { char arr[5] = {'h', 'e', 'l', 'l', 'o'}; function(arr); } "Opinions are neither right nor wrong. I cannot change your opinion. I can, however, change what influences your opinion." - David Crow

doneirik wrote: Is there a way to display integers directly not unless the control has a specific method for displaying integers. most only have methods to display strings. Image Toolkits | Image Processing | Cleek

a char type IS an integer. it just is on 8 bits instead of 16 bits for short or 32 for long. int may be 16, 32 or 64 bits depending on the architecture. TOXCCT >>> GEII power [toxcct][VisualCalc]

it is not neccessary to write in a thread - thread is for waiting (reading) events. before u write, u need to check if writing (sending) buffer is empty - otherwise writing fails. i have worked for years on your current job. includeh10

Thanks, it worked.

Your main thread is blocking on the WaitCommEvent. Typically, code like this would be placed into a separate tread where it would not interfere with the processing of other information, such as mouse movements, painting, keyboard events, etc.

If there is a problem with the data reception, I doubt the problem has anything to do with the timeout values for writing. If the received data differs depending on your writing timeout values it's more likely you have a timing problem accessing the port. If you have opened the port non-overlapped a reading operation will prevent a writing operation until it reaches its timeout and vice versa. Are you sure that no other signals have to be manipulated such as DTR and/or RTS? Usually they have, try with HyperTerminal which sets both RTS and DTR to active state if you select no handshaking. This is easily done with the DCB struct and SetCommState. To nail down the real problem, try this: 1. Do not use read/write timeouts. MSDN tells you how to set this up. 2. Connect to another PC or COM-port and open it with HyperTerminal, see if you can receive expected data sent from HT. Alternate 2: create a loop-back by connecting Rx and Tx (pin 2 and 3) and see if you can read the data you are sending. Hope this helps -- Roger

Actually I don´t know exactly what was the cause... 1. I tried to send the characters using a string or character array. Forgot that en extra "\0" is added. This might have caused some problems. 2.The number of bytes to write parameter in the writefile function: I passed it as an int, then as a short. Had problems with int not with short. Still I don´t understand why or if this really caused the problems, and why it was only with the "\r".. doneirik