C / C++ / MFC

locoone wrote:

is there a way to change the background color of these? and i have a slider that is created after the dialog is opened that needs to be changed to.

HBRUSH CtestMFCDlg::OnCtlColor(CDC* pDC, CWnd* pWnd, UINT nCtlColor)
{
	HBRUSH hbr = CDialog::OnCtlColor(pDC, pWnd, nCtlColor);
	if(nCtlColor== CTLCOLOR_SCROLLBAR)
	{
		hbr=CreateSolidBrush(RGB(0,100,0));
	}
	return hbr;
}

LPSTR lszLogFile;
string strLogFile;
int iNumber;

void myFirstFunction(string)
{<blockquote>//Here is my function definition</blockquote>}

/*
* Outputs a specified string to console
*
* @param string strOutoutVal the value to be outputted
* @param integer iIterations the number of iterations the value should be output
*
* @return void
*
*/

void outputString(string strOutputVal, int iIterations)
{<blockquote>for(int i=0; i<iIterations; i++)</blockquote><blockquote>{</blockquote><blockquote><blockquote>cout << strOutputVal << endl; </blockquote></blockquote><blockquote>}</blockquote>}

capricious_001 wrote:

void myFirstFunction(string){
//Here is my function definition
}

void myFirstFunction(string)
{
    //Here is my function definition
}

Which layout style is the best for my code?<br />
Such style issues are a matter of personal taste. Often, opinions about code layout are strongly held, but probably consistency matters more than any particular style. Like most people, I'd have a hard time constructing a solid logical argument for my preferences. <br />
I personally use what is often called "K&R" style. When you add conventions for constructs not found in C, that becomes what is sometimes called "Stroustrup" style. For example: <br />
<br />
class C : public B {<br />
public:<br />
	// ...<br />
};<br />
<br />
void f(int* p, int max)<br />
{<br />
	if (p) {<br />
		// ...<br />
	}<br />
<br />
	for (int i = 0; i<max; ++i) {<br />
		// ...<br />
	}<br />
}<br />
<br />
This style conserves vertical space better than most layout styles, and I like to fit as much as is reasonable onto a screen. Placing the opening brace of a function on a new line helps me distinguish function definition from class definitions at a glance. <br />
Indentation is very important. <br />
<br />
Design issues, such as the use of abstract classes for major interfaces, use of templates to present flexible type-safe abstractions, and proper use of exceptions to represent errors, are far more important than the choice of layout style. 

neilsolent wrote:

I have tried...setting/unsetting things like _WIN32_WINNT...

#define _win32_WINNT 0x500
#include <windows.h>

void main( void )
{
    QueueUserAPC(0, 0, 0);
}

"The largest fire starts but with the smallest spark." - David Crow

"Judge not by the eye but by the heart." - Native American Proverb

"The largest fire starts but with the smallest spark." - David Crow

"Judge not by the eye but by the heart." - Native American Proverb

Milton KB wrote:

Only thing qe need to do is to call Release() on the COM interface. But if it is a Smart pointer you dont have to do that, smart pointer distructor will take care of this. Thats why its smart pointer.

"The largest fire starts but with the smallest spark." - David Crow

"Judge not by the eye but by the heart." - Native American Proverb