20 yrs of C++, more for C. There is NOTHING wrong with using the (T&) cast. ...cmk The idea that I can be presented with a problem, set out to logically solve it with the tools at hand, and wind up with a program that could not be legally used because someone else followed the same logical steps some years ago and filed for a patent on it is horrifying. - John Carmack

GDI is not obsolete. image processing toolkits | batch image processing

Thanks! Exactly what I needed.

Thanks! I appreciate the advise. Regards, Kylur

>The problem seems to be that the idle message does not cascade on from CMyDialogbar into the CMyPropertySheet. Any ideas? Try handling it yourself. afx_msg LRESULT OnKickIdle(WPARAM,LPARAM); ... ON_MESSAGE(WM_KICKIDLE,OnKickIdle) ... LRESULT CMyDialog::OnKickIdle(WPARAM wp, LPARAM lCount) { UpdateDialogControls(this, TRUE); // the dialog // try pMyPropertySheet->UpdateDialogControls(this, TRUE); // or UpdateDialogControls(pMyPropertySheet, TRUE); // or pMyPropertySheet->UpdateDialogControls(pMyPropertySheet, TRUE); // or ::SendMessage(pMyPropertySheet->GetSafeHandle(), WM_KICKIDLE, wp, lp); return 0; } One might work (I am not sure if this is the right way to do this or if it still works - WM_KICKIDLE is/was internal MFC message). Try it... There might be an extra include for the WM_KICKIDLE that is needed... Good luck! H.

Much appreciated... exactly what I needed. Thank you, Kylur.

The property window displays the properties of the active dialog/class. Remember to click on the dialog or the class implementation file (Open it, and click somewhere) to update the properties window. If this does not help, back up your projects, uninstall both VC6 and VC7, then do a fresh install of VC7. I have never experienced this problem myself, so it might be a result of unsuccesfull installation. -Antti Keskinen ---------------------------------------------- The definition of impossible is strictly dependant on what we think is possible.