C / C++ / MFC

union FloatConverter
{
   float fValue;
   char  Bytes[4];
};

P1P3R wrote:

What I was actually looking for is something along the lines of char bytes[4] = float.

union FloatConverter
{
   float fValue;
   char  Bytes[4];
};
void Test()
{
   FloatConverter converter;
   converter.fValue = 1.23;
   // The converter.Bytes array now contains the float's bytes.
   char floatByte0 = converter.Bytes[0];
   char floatByte1 = converter.Bytes[1];
   char floatByte2 = converter.Bytes[2];
   char floatByte3 = converter.Bytes[3];
}

>> If a window does not have the CS_DBLCLKS style, Windows sends
the following message sequence to the window: WM_LBUTTONDOWN,
WM_LBUTTONUP, WM_LBUTTONDOWN, and WM_LBUTTONUP.

>> If a window does have the CS_DBLCLKS style, Windows sends the
following message sequence: WM_LBUTTONDOWN, WM_LBUTTONUP,
WM_LBUTTONDBLCLK, and WM_LBUTTONUP. That is, the second
WM_LBUTTONDOWN message is replaced by a WM_LBUTTONDBLCLK
message.

LRESULT CALLBACK WndProcTaskBar (HWND hwnd,UINT uMsg,WPARAM wParam,LPARAM lParam)<br />
{<br />
	switch (wParam) //Depending on the messsage.<br />
	{	<br />
	case WM_LBUTTONDOWN:<br />
	case WM_LBUTTONUP:<br />
	case WM_LBUTTONDBLCLK:<br />
	case WM_NCLBUTTONDOWN:<br />
	case WM_NCLBUTTONUP:<br />
..........

Christian Graus wrote:

1 - as well as turning themes on, it specifies which versions of dlls your app uses.

2 - in your linker properties, you can get a manifest auto generated and embedded in your app