C / C++ / MFC

nayeemkhan wrote:

Can anyone explain the reason for this high x and y values?

nayeemkhan wrote:

We have a formula that converts this x and y value info into a index number,which we use to retrieve info

nayeemkhan wrote:

I have already coded the validation of x and y (which u suggested)

nayeemkhan wrote:

Can we get a boo/tutorial which explains exactly how CPoint structure gets the x and y values?

nayeemkhan wrote:

Now our customer have given us a crash dump in which CPoint x and y value has 5882 and 1150 which are very huge.

void CHierDispWnd::OnLButtonDown( UINT , CPoint Point  )//HERE point.x is 5882 and point.y is 1150
{
	
   int ListClick;
   long MemClick;
   int GapX,GapY;
   GapX = m_pStdProps->m_iGapX;//GapX = 16
   GapY = m_pStdProps->m_iGapY;//Gapy = 10
   int mem_wd,mem_ht;
   mem_wd = m_pStdProps->m_iMemWidth;//mem_wd =125
   mem_ht = m_pStdProps->m_iMemHeight;//mem_ht=18
   SetFocus();
   if ((Point.x < CXSCROLLBTN) || (Point.y < GapY))//CXSCROLLBTN = 16
      return;
   ListClick = (Point.x - CXSCROLLBTN) / (mem_wd + GapX);//HERE WE ARE CONVERTING point.x to ListClick
   if (!pMiddle->ListValid( ListClick))//CRASHES IN THIS FUNC...LISTCLICK is 41,which does not    
                                          //exists
          return;
}

nayeemkhan wrote:

if (!pMiddle->ListValid( ListClick))//CRASHES IN THIS FUNC...LISTCLICK is 41,which does not //exists

strConfig.Format("CREATE_DB=\"%s\"\0SystemDB=my workgroup.mdw"
							"\0UID=Pani\0\0",m_fileName);

CREATE_DB="whatever m_fileName is"

std::basic_string<TCHAR> s;
s = _T("CREATE_DB=\""); s+= m_fileName ; s += _T("\"");
s += TCHAR(0);
s += _T("SystemDB=my workgroup.mdw");
s += TCHAR(0);
s += _T("UID=Pani");
s += TCHAR(0);
s += TCHAR(0);
s += TCHAR(0);

char szConfig[1024];

sprintf(szConfig,"SystemDB=%s%cUID=%s%cCREATE_DB=\"%s\"%c%c",
		"my workgroup.mdw",'\0',"Pani",'\0',m_fileName,'\0','\0');

SQLConfigDataSource(NULL, ODBC_ADD_DSN, strAccessDriver,szConfig);

pani68 wrote:

Now it is working fine.

CString cstring(reinterpret_cast<wchar_t*>(lpvoid));

Code-o-mat wrote:

Hey!

On a side note: having a button that gets enabled when a correct password is entered makes it a bit easier to guess the password by bruteforce (or/and maybe other methods) because one only has to write a program that enters a password and then checks the state of the button, if it is disabled, it tries the next possible password and checks the button again until the button becomes enabled... althorough you can add a -let's say- 3 seconds pause if a wrong password is entered before the user is allowed to enter the next password, this makes it take much much more time to hack.

Code-o-mat wrote:

Aside of this, did you try handling WM_KEYDOWN? Did it work?

case WM_CHAR : 
{
	switch(LOWORD(wParam))
	{
		case VK_RETURN:
			MessageBox(hWnd, "Enter Pressed", NULL, NULL);
	}
}

case WM_KEYDOWN : 
{
	switch(LOWORD(wParam))
	{
		case VK_RETURN:
			MessageBox(hWnd, "Enter Pressed", NULL, NULL);
	}
}