C / C++ / MFC

Ravindra_Joshi wrote:

UINT nPlanes , UINT nBitcount ( I think these values might be causing a problem..)

For a color bitmap, either the nPlanes or nBitcount parameter 
should be set to 1. If both of these parameters are set to 1, 
CreateBitmap creates a monochrome bitmap.

For a 16x16 bimap nPlanes==4, nBitcount==1 the data is layed out in the array<br />
Plane 0, Row 0 2 bytes<br />
Plane 0, Row 1 2 bytes<br />
...<br />
Plane 0, Row 15 2 bytes<br />
Plane 1, Row 0 2 bytes<br />
Plane 1, Row 1 2 bytes<br />
...<br />
Plane 1, Row 15 2 bytes<br />
...etc

For a 16x16 bimap nPlanes==1, nBitcount==24 the data is layed out in the array<br />
Plane 0, Row 0 48 bytes<br />
Plane 0, Row 1 48 bytes<br />
...<br />
Plane 0, Row 15 48 bytes

//Forward declaration
class CMyAwkwardClass;

//Declare a class that uses CMyAwkward even though we don't know what it is yet
class CSomeOtherClass
{
  private:

  CMyAwkwardClass* m_pAwkward;
};

Electronic75 wrote:

CMyAwkwardClass* m_pAwkward manually when exiting the program to prevent memory leakage

Rage wrote:

Only if you initialize it using the new operator or a copy constructor or ..., not if it is only used as a pointer.

LRESULT CIdleTestDlg::OnKickIdle(WPARAM wp, LPARAM lp)<br />
{<br />
	MSG msg;<br />
	if(GetMessage(&msg,NULL,0,0x300)){		<br />
			DispatchMessage(&msg);<br />
	}<br />
	return 0L;<br />
}

The following are the ranges of message numbers. 

Range                  Meaning 
0 through WM_USER–1    Messages reserved for use by the system. 
WM_USER through 0x7FFF Integer messages for use by private window classes. 
WM_APP through 0xBFFF  Messages available for use by applications. 
0xC000 through 0xFFFF  String messages for use by applications. 
Greater than 0xFFFF    Reserved by the system. 

// Add to the dialog's .h file:
  
afx_msg LRESULT OnMIMLongData(WPARAM wp, LPARAM lp);
 
 
// Add to the dialog's .cpp file:
 
// Add to the dialog's message map
ON_MESSAGE(MM_MIM_LONGDATA, &CMyDlg::OnMIMLongData)
 
LRESULT CMyDlg::OnMIMLongData(WPARAM wParam, LPARAM lParam)
{
   HMIDIIN MIDIDeviceHandle = (HMIDIIN)wParam;
   MIDIHDR *pMIDIHdr = (MIDIHDR *)lParam;
 ...
   return 0;
}

Mark Salsbery wrote:

You may get better performance if you use a callback function instead of window messages.

Mark Salsbery wrote:

What window handle are you passing when you call midiInOpen()?
When are you calling midiInOpen()?

HMIDIIN hdlMidiIn = NULL;<br />
MMRESULT mReturnCode=MMSYSERR_NOERROR;  <br />
CWnd* pMainDialog = (CWnd*)AfxGetApp()->m_pMainWnd;<br />
HWND hWnd = pMainDialog->m_hWnd;<br />
mReturnCode = midiInOpen(&hdlMidiIn,uhInID,(DWORD)hWnd,(DWORD)NULL,CALLBACK_WINDOW);<br />

LRESULT CMIDIDlg::OnKickIdle(WPARAM wp, LPARAM lp)<br />
{<br />
	MSG msg;<br />
	if(GetMessage(&msg,NULL,0,MM_MIM_LONGDATA)){<br />
		if(msg.message != WM_KICKIDLE)<br />
			DispatchMessage(&msg);<br />
	}<br />
	return 0L;<br />
}<br />