Search:

Only use delete on the memory that you have allocated (object = new Whatever;) or where it is documented to do so. You are not allocating any memory with your call to GetDlgItem. You are just...

You may find it silly, but I can't imagine why you'd actually want to design something this way. If this is the best solution, then it's time to go back to the drawing board.

I would do the validation when they're ready to close the dialog instead of when the control loses focus. That way, if they're hitting cancel, you don't need to do any validation... you just close.

CWnd* helpButton = GetDescendantWindow(IDHELP);

if (helpButton)
{
helpButton->ShowWindow(SW_HIDE);
}

You can't have a Next and Finish button on the same page. It's either one or the other. Take out PSWIZB_NEXT and you'll get a disabled Finish button.

In your rc file, give each radio button the BS_AUTORADIOBUTTON style. Then you don't have to write a lot of cumbersome code to unselect one radio button after selecting another.

Just look at the amount of posts for Visual C++ in this forum compared to C# and .net. Until those numbers start changing, I wouldn't worry about it going away.

Time to redesign!

Got a strange linking error here that I've never seen before.

LINK : fatal error LNK1201: error writing to program database
"E:\st\ST\Debug\cmsAppDB.pdb"; check for insufficient disk space
...

BOOL CMainFrame::PreCreateWindow(CREATESTRUCT& cs)
{
// Get rid of Untitled in title bar
cs.style &= ~(LONG) FWS_ADDTOTITLE;

if( !CFrameWnd::PreCreateWindow(cs) ) {
return FALSE;...

Never mind... I figured it out. I'm actally looking for an LVN_ITEMCHANGED notification. The reason I wasn't getting the LVN_ODSTATECHANGED is because it's not an ownerdrawn control. Whoops.

Does anyone know how the LVN_ODSTATECHANGED notification is used or when this notification gets sent. I thought that this notification was sent when the state of one the items in the list control...

Thanks for the reply... I'm not quite sure I understand though. Can you explain a little further about subclassing the control?

I am experimenting with a CListCtrl class. Through AppWizard, I create a dialog based app and also created a new class which inherits from CListCtrl. I then used Resource editor to add a list...

Thanks for the reply... but why is that code generated in the first place? Take that code out or comment out that code and everything seems to run normally. So why is it generated in the first...

App Wizard will generate the following code in .cpp files.

#ifdef _DEBUG
#undef THIS_FILE
static char THIS_FILE[] = __FILE__;
#endif



Does anyone out there know what this code does? MSDN...

Buy bigger screens :-)

The application I work on at my job uses Far Point controls and another 3rd party vendor which makes Widget controls. Believe me, all the third party controls we use stink... I wish we were using...

Put the SetRedraw calls on either side of the for loop.


SetRedraw(FALSE);
for (whatever)
{
}
SetRedraw(TRUE);

If you know for sure that an exception is being thrown, then it must not be of type CException. Put another catch below that one:

catch (...) /* this is to catch everything not already caught*/...

You'd be better of just making the dialog yourself. Less of a hassle.

Use a list (i.e. CList), instead... then who cares how many elements you have in the list.

Pass the handle of the window to the new thread (the m_hWnd member). Then use the static CWnd::FromHandle method to "recreate" your CWnd in the worker thread passing it the handle of your window.

Buy InstallShield.

If they told you not to use C++, then they probably don't know how to use it themselves. VB or Java... blah!