C / C++ / MFC

Mike Dimmick11-Aug-03 11:13

Mike Dimmick

11-Aug-03 11:13

There's no end-of-list mark with variable argument lists. You've been lucky so far that, sometimes, the next item on the stack has been zero.

You need to either look for a terminator value, or know how many items are in your list (by, for example, passing that as the first argument).

leppie11-Aug-03 11:23

leppie

11-Aug-03 11:23

OK that just plain sux.... it will be easeir just to pass a linked list.

leppie ::AllocCPArticle(Generic DFA State Machine for .NET);

geo_m12-Aug-03 1:06

geo_m

12-Aug-03 1:06

hmm, maybe, but then you'll loose some of the type of comfort that (...) provides. Imagine that before every printf() you have to prepare a linked list of arguments :-/.

But on the other side, the ... parameters doesn't have the type control, so it's some sort of evil Wink | ;-)

leppie12-Aug-03 7:13

leppie

12-Aug-03 7:13

My hack is just pass a NULL at the end....

leppie ::AllocCPArticle(Generic DFA State Machine for .NET);

lossing focus on a dialog box

geo_m12-Aug-03 7:34

geo_m

12-Aug-03 7:34

Any way, that allows you to detect end of the parameter list is acceptable. With the NULL backstop is only one disadvantage which comes to mind when you really need to pass some NULL as a valid value to one of normal parameters.

(Steven Hicks)ⁿ⁺¹11-Aug-03 10:34

(Steven Hicks)ⁿ⁺¹

11-Aug-03 10:34

I created a Modaless dialog from my application, how can I detect that the dialog has lost focus (ex when the user clicks within the parent window and the dialog box is still there. I need this b/c without it new Modaless dialog boxes can be created with the existing one there.

-Steven Hicks

CPA

CodeProjectAddict

Actual Linux Penguins were harmed in the creation of this message.

More tutorials: Ltpb.8m.com: Tutorials |404Browser.com (Download Link)

Re: lossing focus on a dialog box

valikac11-Aug-03 12:08

valikac

11-Aug-03 12:08

One solution is to add a handler for WM_KILLFOCUS.

Kuphryn

COM1

Anonymous11-Aug-03 9:54

11-Aug-03 9:54

who to flush the receivebuffer of the serial interface (com1)

David Crow11-Aug-03 10:33

11-Aug-03 10:33

How are you currently reading from it?

Anonymous11-Aug-03 11:26

11-Aug-03 11:26

#ifndef MESSGERAETE_H
#define MESSGERAETE_H

#include "windows.h"

class Messgeraete{

public:

Messgeraete();
~Messgeraete();

void takeValues();
double getValue(int value);
void stopThread();

//-1: Messung wurde abgerochen, 0 keine gütligen Werte, 1 gültige Werte wurden gelesen
int getMessflag();

static DWORD messenThread(LPVOID);

private:

HANDLE h_com;
HANDLE h_messThread;

DCB dcb;
COMMTIMEOUTS cto;

double value1, value2;
int messflag;

};

#endif

Messgeraete::Messgeraete(){

messflag=0;

h_com = CreateFile("COM1", GENERIC_READ | GENERIC_WRITE, 0, NULL, OPEN_EXISTING, 0 , NULL);

DCB dcb_neu;
COMMTIMEOUTS cto_neu;

GetCommState(h_com, &dcb);
GetCommState(h_com, &dcb_neu);

dcb_neu.BaudRate = 9600;
dcb_neu.ByteSize = 8;
dcb_neu.Parity = NOPARITY;
dcb_neu.StopBits = ONESTOPBIT;
SetCommState(h_com, &dcb_neu);

GetCommTimeouts(h_com,&cto);
GetCommTimeouts(h_com,&cto_neu);
cto_neu.ReadTotalTimeoutConstant=0;
cto_neu.ReadTotalTimeoutMultiplier=0;
SetCommTimeouts(h_com,&cto_neu);

}

Messgeraete::~Messgeraete(){

SetCommTimeouts(h_com,&cto);
SetCommState(h_com, &dcb);
CloseHandle(h_com);

}

DWORD Messgeraete::messenThread(LPVOID lparam){

Messgeraete *mp = (Messgeraete*)lparam;

int i;
unsigned long nBytesRead1,nBytesRead2;
char inbuffer1[13];
char inbuffer2[13];

char temp[9];
temp[8]=0;

ReadFile(mp->h_com, &inbuffer1, 13, &nBytesRead1, NULL);
ReadFile(mp->h_com, &inbuffer2, 13, &nBytesRead2, NULL);

// CString str;
// str.Format("%s\n%s",inbuffer1,inbuffer2);
// AfxMessageBox(str);

for(i=0;i<8;i++) temp[i]=inbuffer1[i+4];
mp->value1=atof(temp);

for(i=0;i<8;i++) temp[i]=inbuffer2[i+4];
mp->value2=atof(temp);

if(inbuffer1[0]=='9'){mp->value1=-1;AfxMessageBox("Messschieber ist nicht eingeschaltet oder nicht richtig angeschlossen");}
if(inbuffer2[0]=='9'){mp->value2=-1;AfxMessageBox("Messuhr ist nicht eingeschaltet oder nicht richtig angeschlossen");}

mp->messflag=1;

return 0;

}

void Messgeraete::takeValues(){

messflag=0;
h_messThread=CreateThread(NULL, 0, (LPTHREAD_START_ROUTINE)messenThread, (LPVOID)this, 0, NULL);

}

double Messgeraete::getValue(int value){

if (value==1) return value1;
else return value2;

}

void Messgeraete::stopThread(){

DWORD dw;
GetExitCodeThread(h_messThread, &dw);
TerminateThread(h_messThread, dw);
value1=value2=-1;
messflag=-1;

}

int Messgeraete::getMessflag(){ return messflag; }

David Crow12-Aug-03 2:35

12-Aug-03 2:35

FlushFileBuffers(h_com);

Anonymous12-Aug-03 3:34

12-Aug-03 3:34

doesn't work

in msdn is writte:
If hFile is a handle to a communications device, the function only flushes the transmit buffer.

I want to flush the receive buffer

any ideas?

Anonymous12-Aug-03 9:21

SOS! Release version crashed

12-Aug-03 9:21

Hi David,
Solution was this command
Thanks for you help

PurgeComm(h_com,PURGE_RXCLEAR);

lucy11-Aug-03 9:28

lucy

11-Aug-03 9:28

yes, the debugging version is working okay, and the release version crashed.

It's a SDI project. After the release version run for about 5 seconds, this error message pop up:
"First-chance exception in MyApp.exe: 0xC0000005: Access Violation."

The call stack is:

CWnd::AttachControlSite(CWnd * const 0x010b7b2c {CMapPtrToPtr}, CHandleMap * 0x010b7b28) line 420
CWnd::FromHandle(HWND__ * 0x00060aaa) line 293
CWnd::GetOwner(const CWnd * const 0x010b7b2c {CMapPtrToPtr}) line 35 + 22 bytes
AfxGetParentOwner(HWND__ * 0x00050ad2) line 2141 + 7 bytes
CWnd::GetTopLevelParent(const CWnd * const 0x010b7b2c {CMapPtrToPtr}) line 2157 + 6 bytes
CWinThread::PreTranslateMessage(CWinThread * const 0x010b7b2c {CMapPtrToPtr}, tagMSG * 0x004751d0 {msg=0x00000118 wp=0x0000ffff lp=0xa00258ae}) line 680 + 7 bytes
CWinThread::PumpMessage(CWinThread * const 0x010b7b2c {CMapPtrToPtr}) line 848 + 17 bytes
CWinThread::Run(CWinThread * const 0x010b7b2c {CMapPtrToPtr}) line 487 + 7 bytes
CWinApp::Run(CWinApp * const 0x010b7b2c {CMapPtrToPtr}) line 399 + 7 bytes
AfxWinMain(HINSTANCE__ * 0x00400000, HINSTANCE__ * 0x00000000, char * 0x00133476, int 1) line 49 + 7 bytes
WinMain(HINSTANCE__ * 0x00400000, HINSTANCE__ * 0x00000000, char * 0x00133476, int 1) line 30
TCSTATUS! WinMainCRTStartup + 224 bytes

any hint?

Thank you a lot for any help!

Maximilien11-Aug-03 9:41

Maximilien

11-Aug-03 9:41

The usuals, check for un-initialized variables, bad conditions in if, bad loops, ...

Give your project a level-4 warning level compile to see if the compiler can find the obvious things.

Maximilien Lincourt
"Never underestimate the bandwidth of a station wagon filled with backup tapes." ("Computer Networks" by Andrew S Tannenbaum )

David Crow11-Aug-03 9:48

11-Aug-03 9:48

See if this helps:

http://flounder.com/debug_release.htm

lucy11-Aug-03 9:53

lucy

11-Aug-03 9:53

Thank you guys. Rose | [Rose]

I used a class for joystick support. I think it's it which couldn't survive the release. Dead | X|

I used it in another app, which I couldn't build release version either.

It's using DirectIO tech. Any idea how to debug such stuff?

David Crow11-Aug-03 10:32