C / C++ / MFC

pix_programmer7-Jun-11 2:49

pix_programmer

7-Jun-11 2:49

Stefan_Lang wrote:
- have you applied any patches?

For other questions my answer is 'no'.

I didn't understand what is "patches". I've created Mutex. But it was working fine with Mutex. Here's my Mutex code:

BOOL Cflash_mfcApp::InitInstance()
{
	// InitCommonControlsEx() is required on Windows XP if an application
	// manifest specifies use of ComCtl32.dll version 6 or later to enable
	// visual styles.  Otherwise, any window creation will fail.
	INITCOMMONCONTROLSEX InitCtrls;
	InitCtrls.dwSize = sizeof(InitCtrls);
	// Set this to include all the common control classes you want to use
	// in your application.
	InitCtrls.dwICC = ICC_WIN95_CLASSES;
	InitCommonControlsEx(&InitCtrls);

	CWinApp::InitInstance();

	AfxEnableControlContainer();


#ifdef _AFXDLL
	Enable3dControls();			// Call this when using MFC in a shared DLL

#else
	Enable3dControlsStatic();	// Call this when linking to MFC statically
#endif
	// Standard initialization
	// If you are not using these features and wish to reduce the size
	// of your final executable, you should remove from the following
	// the specific initialization routines you do not need
	// Change the registry key under which our settings are stored
	// TODO: You should modify this string to be something appropriate
	// such as the name of your company or organization
	SetRegistryKey(_T("Local AppWizard-Generated Applications"));





	Default();
	FileRead();
	char CurrentPath[_MAX_PATH];
	Gen ObjGen;
	ObjGen.GetCurrentPath(CurrentPath);
	ostringstream OCurrPath;
	OCurrPath.str("");
	OCurrPath << CurrentPath<<"\\";
	CurrPath="";
	CurrPath = OCurrPath.str();


	if(NULL != ::CreateMutex(NULL, TRUE,_T("CSingleInstanceApp")))
	{
		long dwError = ::GetLastError();
		if(dwError == ERROR_ALREADY_EXISTS)
		{
			//	MessageBox(NULL,L"You are Already Running Application.",L"ERROR!!",MB_OK);
			EndDialog(NULL,IDOK);	
			return FALSE;
		}
		else
		{
			/*Update *ObjUpdate=new Update;
			ObjUpdate->Create(IDD_UPDATE,this);
			ObjUpdate->ShowWindow(SW_SHOW);*/


			if(!ObjGen.OnCheckConnection())
			{
				CError ObjCError;
				m_pMainWnd = &ObjCError;
				INT_PTR nResponse = ObjCError.DoModal();
				//ObjCError.DoModal();
				return 0;
			}


			ostringstream oexe;
			oexe << "cmd /c del "<<glo_exe_name<<"_* /f/q/a";
			WinExec((LPCSTR)oexe.str().c_str() , SW_HIDE);

			Update ObjUpdate;
			m_pMainWnd = &ObjUpdate;
			INT_PTR nResponse = ObjUpdate.DoModal();

			AfxGetApp()->m_pMainWnd = NULL;

			
		TerminateThread(Retry::ThreadExec, 0);
		TerminateThread(TransferringForm::ThreadExec, 0) ;
		TerminateThread(TransferringForm::ThreadExec1, 0) ;

		ostringstream os;
		os << "cmd /c taskkill /F /IM \"" << glo_exe_name <<"\" /T";
		string to=os.str();
		WinExec((LPCSTR)to.c_str() , SW_HIDE);
		}

		
	}


	/*Cflash_mfcDlg dlg;
	m_pMainWnd = &dlg;
	INT_PTR nResponse = dlg.DoModal();

	if (nResponse == IDOK)
	{
	IndexForm ObjIndexForm;
	m_pMainWnd = &ObjIndexForm;
	ObjIndexForm.DoModal();
	}
	else if (nResponse == IDCANCEL)
	{


	}*/



	// Since the dialog has been closed, return FALSE so that we exit the
	//  application, rather than start the application's message pump.
	return FALSE;
}

But my app was working fine with this code.

Stefan_Lang7-Jun-11 2:55

Stefan_Lang

7-Jun-11 2:55

Erm, no, I was referring to updates to your IDE, to your version of .NET or to Windows.

The reason for this question is that a change to the MFC dll could be responsible. Not a very likely scenario, but it happens.

pix_programmer7-Jun-11 3:00

pix_programmer

7-Jun-11 3:00

I installed vcredist_x86.exe. Is it possible to uninstall that? If not what are the dlls that nedd to be replaced? Where?

Display CBitmap into CStatic [modified]

Stefan_Lang7-Jun-11 3:26

Stefan_Lang

7-Jun-11 3:26

You may not need to uninstall it, and I'm not sure that would be advisable either.

But since vcredist_x86.exe installs the newest version of MFC, it's possible the lib has changed, and therefore you need to rebuild your application, using the new lib and headers.

Alternately you can force your application to use the old version of the MFC dll by copying that version into the same directory as your executable. Your IDE probably keeps its own copy. For instance on my PC I can find various versions of the MFC under C:\Program Files\Microsoft Visual Studio\VSS\netsetup.x86\VSS\win32

_Flaviu6-Jun-11 1:54

_Flaviu

6-Jun-11 1:54

Please tell me what I am doing wrong because in CStatic I didn't see anything :

BOOL CMyPage::OnInitDialog() 
{
	CPropertyPage::OnInitDialog();

	// TODO: Add extra initialization here

	CBitmap bitmap;
	bitmap.LoadBitmap(IDB_BITMAP1));
	m_staticIcon.SetBitmap((HBITMAP)bitmap);

	return TRUE;  // return TRUE unless you set the focus to a control
	              // EXCEPTION: OCX Property Pages should return FALSE
}

Of course m_staticIcon have SS_BITMAP style.
Thank you.

modified on Monday, June 6, 2011 8:06 AM

Re: Display CBitmap into CStatic

Roger Allen6-Jun-11 2:24

Roger Allen

6-Jun-11 2:24

If you vote me down, my score will only get lower

Re: Display CBitmap into CStatic

_Flaviu6-Jun-11 2:39

_Flaviu

6-Jun-11 2:39

You are perfectly right ! Thank you very much ! Best wishes !!!

CStatic ModifyStyle

_Flaviu6-Jun-11 1:00

_Flaviu

6-Jun-11 1:00

I don't know why can not modify style at runtime : at design time style of CStatic is Frame , and in OnInitDialog I try :

m_staticIcon.ModifyStyle(0,SS_BITMAP | SS_CENTERIMAGE);
m_staticIcon.SetBitmap(::LoadBitmap(AfxGetApp()->m_hInstance, MAKEINTRESOURCE(IDB_BITMAP1)));

but didn't working at all ( I seen nothing on dialog ) ... what I should to do modify style in SS_BITMAP ?
Thank you.

Re: CStatic ModifyStyle

The_Inventor6-Jun-11 20:41

The_Inventor

6-Jun-11 20:41

My bet is that as the CBitmap is a local object it goes out of scope at the end of the function and its destructor cleans up its memory usage and deletes the bitmap you loaded.

Try making it a member variable instead.

The above is an answer from another question, however I think it applies. Member varibles in the class, tend to be less volitile. If the varible is in your "CMyDoument" class, it is more prone to persistance.

The World as we think we know it Has a lot more to it than meets the eye.

A Mad Scientist who has seen it for himself....

Re: CStatic ModifyStyle

Code-o-mat7-Jun-11 22:59

How to use tcp keepalive to check the client is alive?

7-Jun-11 22:59

Try also removing the old style (first parameter of ModifyStyle), however, not every style can be changed at runtime, i don't know which can and can't, you should google it up.

> The problem with computers is that they do what you tell them to do and not what you want them to do. <
> //TODO: Implement signature here<

wangningyu4-Jun-11 23:23

wangningyu

4-Jun-11 23:23

I use the WSAAsyncSelect now, and then the server use the vector to save the client.

the server has a ListCtrl to show the online's client,and then FD_ACCEPT it will push_back into the vector.

and then FD_CLOSE it will earse from the vector.

but it often not receive FD_CLOSE when the client's power failure.

I found the setsockopt from google, but don't quite understand the Windows Socket TCP Keepalive.

how to use it ?

Thanks for your reply !

Re: How to use tcp keepalive to check the client is alive?

Code-o-mat5-Jun-11 22:55

Re: How to use tcp keepalive to check the client is alive?

5-Jun-11 22:55

MSDN[^] states:
If a connection is dropped as the result of keep-alives the error code WSAENETRESET is returned to any calls in progress on the socket, and any subsequent calls will fail with WSAENOTCONN.

If keep-alive is enabled for a TCP socket with SO_KEEPALIVE, then the default TCP settings are used for the keep-alive timeout and interval unless these values have been changed by calling the WSAIoctl function with the SIO_KEEPALIVE_VALS option.

Also, here[^] it says:
For TCP, the default keep-alive timeout is 2 hours and the keep-alive interval is 1 second. The default number of keep-alive probes varies based on the version of Windows.

Also, this[^] states:
KeepAliveTime
Specifies how often TCP sends keep-alive transmissions. TCP sends keep-alive transmissions to verify that an idle connection is still active.
This entry is used when the remote system is responding to TCP...

and here[^]:
KeepAliveInterval
Specifies how often TCP repeats keep-alive transmissions when no response is received.

So this whole thing boils down -to me at least- to this:
1. If this is enabled you will receive WSAENETRESET or WSAENOTCONN if you try to read or write the socket in case the "other side" disappeared.
2. By default, the system "pings" the other side every 2 hours, if no answer is received it will start "pinging" it every second who-knows-how many times before giving up. 2 hours is a lot of time, you might want to shorten that.

> The problem with computers is that they do what you tell them to do and not what you want them to do. <
> //TODO: Implement signature here<

Emilio Garavaglia6-Jun-11 3:41

Emilio Garavaglia

6-Jun-11 3:41

Code-o-mat wrote:
2 hours is a lot of time, you might want to shorten that.

Dangerous: those timers are expected to be consistent on a very wide number of system, and -because of the way TCP works- there is no need to make it shorter.

The keep-alive is sent on a silent socket to let it be not-anymore silent. But the problem is ... why is it silent?

If there are data to let flow, TCP itself recover transmission error and - if that cannot be done - reports to the soket WSAENETRESET/WSAENOTCONN independently on every keep-alive feature.
If there are no data to let flow for long time, considering servers queue, routing tables, switches cam table, firewall caches, ARP table etc. assuming everything still works the same is risky. Better to close the socket, and reopen it again when furtherly needed, and use some "session layer command or data" (the application should define what the y should be) to track the state of the session or re-sync the client and the server.

In other words, the OP had better to implement a more robust application protocol that uses the underlying socket not just to transfer data, but also to exchange some status information about the existence and activity of the client and the server (this can be done more frequently) if he wants to promptly react to an unexpected event.

2 bugs found.
> recompile ...
65534 bugs found.
D'Oh! | :doh:

Re: How to use tcp keepalive to check the client is alive?

Code-o-mat6-Jun-11 3:58

Re: How to use tcp keepalive to check the client is alive?

6-Jun-11 3:58

That all might be true but he asked how keepalive works (and correct me if i am wrong in what i answered to that), not how he should design his client/server protocol. Smile | :)

I agree that instead of relying on keepalive he should implement his own mechanism for detecting if the other side is gone because that would give him a much better control over the whole thing, but of course, that's just my oppinion. To detect if a long-silent connection is silent because the other side doesn't have anything to say OR because someone poured some coffee over the router would require -as far as i know- some kind of "pinging" and "timeouting", and keepalive does exactly that, so the aproach isn't fundamentally flawed.

For the "shortening of the 2 hours thing", as i understood you can set the timings for sockets individually, i meant that, not fiddlign with the system-wide settings.

> The problem with computers is that they do what you tell them to do and not what you want them to do. <
> //TODO: Implement signature here<

jschell6-Jun-11 9:07

jschell

6-Jun-11 9:07

Koma Wang wrote:
how to use it ?

Simple - don't.

No one wants to know if a connection is alive. What they want to know is whether the business logic is still functioning. And the only way to do that is to implement something that actually tests the functionality. The more fully it tests it the better. But at a minimum you can assure that the server is at least still responding to a message enough to return a response.

A simple implementation is to send a do nothing request from the client at a configured interval if no other request has been sent in that period.

And do NOT rely on such functionality to get around error checking legitimate requests. A server can go down right in the middle of a legitimate request.

mysql error and UNICODE

includeh104-Jun-11 18:44

includeh10

4-Jun-11 18:44

mysql returns an error, which contains UNICODE string in whole char* error string as following:

Duplicate entry 'MQ91' for key 'UnicodeName'

here 'MQ91' is UNICODE string but can not be recognized.

How to transfer the English/UNICODE mixed error string above in right format,
or how to know the 'MQ91' is UNICODE?

Re: mysql error and UNICODE

Code-o-mat5-Jun-11 22:26

Is it possible to set another visual style only for my application [modified]

5-Jun-11 22:26

What do you mean by "transfer"?
If you are using printf or Format or somesuch, you can use %ls for unicode strings, like:

CString msg;
msg.Format("This is a unicode string: %ls", unicode_string);

You can also use WideCharToMultiByte[^] to convert a unicode string to MBCS (or ASCII?).
Does any of this help?

> The problem with computers is that they do what you tell them to do and not what you want them to do. <
> //TODO: Implement signature here<

Cold_Fearing_Bird4-Jun-11 16:59

Cold_Fearing_Bird

4-Jun-11 16:59

Can I use SetWindowTheme to set another set of visual style exclusively for my application ?
For example, My system use window7 style. But I want my application to use WindowXP or a custom style.

modified on Sunday, June 5, 2011 1:47 AM

Re: Is it possible to set another visual style only for my application

Rotted Frog6-Jun-11 20:46

Rotted Frog

6-Jun-11 20:46

No. You can't have application specific themes. If you need that sort of functionality, look at custom UI frameworks. The recent versions of MFC have skinned controls, which offer different visual styles (Office 2007, VS2008 etc.) Also third party MFC control vendors like BCGSoft or Codejock offer a lot of skinnable controls.

[Win32] How draw a rectangle on the desktop

Member 29654714-Jun-11 9:34

Member 2965471

4-Jun-11 9:34

Hi, I'm trying to draw a rectangle on the screen with MouseHook, but i can't:

LRESULT CALLBACK MouseProc(int nCode,WPARAM wParam,LPARAM lParam)
{
LPMOUSEHOOKSTRUCT info=(LPMOUSEHOOKSTRUCT) lParam;
static BOOL capturing = 0;
Pen p(Color(255,255,0,0),5);
Graphics g(GetDC(0));

switch(wParam)
{
case WM_LBUTTONDOWN:
capturing = TRUE;
rcCaptured.left = info->pt.x;
rcCaptured.top = info->pt.y;
break;
case WM_LBUTTONUP:
if( capturing )
{
rcCaptured.right = info->pt.x;
rcCaptured.bottom = info->pt.y;
capturing = FALSE;
}
break;
case WM_MOUSEMOVE:
InvalidateRect(GetDesktopWindow(),NULL,FALSE);
g.DrawRectangle(&p,rcCaptured.left,rcCaptured.top,info->pt.x-rcCaptured.left,info->pt.y-rcCaptured.top);
break;
}
}

how can force repaint of the screen? and how remove hook after select a rectangle?

Mark Salsbery4-Jun-11 11:16

Mark Salsbery

4-Jun-11 11:16

I'm guessing your InvalidateRect() call is causing a repaint that ends up covering up what you just drawed to the screen.

What is happening with your current code??

Mark Salsbery
Microsoft MVP - Visual C++
Java | [Coffee]

Member 29654714-Jun-11 11:51

Member 2965471

4-Jun-11 11:51

InvalidateRect doesn't work, the screen is still dirty.

Mark Salsbery4-Jun-11 11:56

Mark Salsbery

4-Jun-11 11:56

Yes, you'd have to set the erase background flag to true in the call and call UpdateWindow() to force an immediate paint. That worked on older OSs but on Windows 7 the updates don't happen while you have the mouse button pressed it seems. It does work on the LBUTTONUP message (just tested it).

You may have to double buffer - grab the image for the rect from the screen, draw your rectangle, draw the captured image back to the screen to erase, etc.

Mark Salsbery
Microsoft MVP - Visual C++
Java | [Coffee]