Property sheet in dialog

Josef Vosyka -- josef.vosyka@vsb.cz
Monday, February 05, 1996

Hi,

I need to have Property sheet placed into a dialog. I have solved 
this problem by putting the follow line into "OnInitDialog()"

	m_appsSheet.Create(this, WS_CHILD|WS_VISIBLE|WS_SYSMENU, 0);

where
	"m_appsSheet" is member of "CPropertySheet" kind.

The problem is that the property sheet created this way does not 
process TAB key strokes. I've tried to override 
"CDialog::PreTranslateMessage(MSG* pMsg)" function, but the dialog 
does not call it. Not even "PreTranslateMessage" functions in 
CPropertyPage and CPropertySheet.

It really drives me crazy. Does anybody know why the 
"PreTranslateMessage" functions are not called or how to get TABs 
into action ??? Or is this way of putting property sheet into a 
dialog the right one ?


	Thanks in advance.
									Joseph


.....
VOSYKA Josef -> SW Engineering, Neural Networks, OOP, Win* Apps
voice (42)69-699 5443, fax (42)69-691 9597
email: Josef.Vosyka@vsb.cz, http://www.vsb.cz/~bs88128

---

Mallikarjuna -- mallik@pune.gssl.ernet.in
Monday, February 12, 1996


Mr.Josef,
> 
> I need to have Property sheet placed into a dialog. I have solved 
> this problem by putting the follow line into "OnInitDialog()"
> 
> 	m_appsSheet.Create(this, WS_CHILD|WS_VISIBLE|WS_SYSMENU, 0);
Why don't you Create the property sheet in OnSetActive() instead of OnInitDialog(); I have implemented the same and it's working fine.
> 
> It really drives me crazy. Does anybody know why the 
> "PreTranslateMessage" functions are not called or how to get TABs 
> into action ??? Or is this way of putting property sheet into a 
> dialog the right one ?
> 
	I feel OnInitdialog is too young to unserstand the TAB keystrokes. I feeel OnSetActive is the right place instead.I hope this will solve your problem.


Regards,
Mallikarjun.

---

| Вернуться в корень Архива |