I've been experimenting with the Peter Stephensen's DDTTab code, and
I have a few questions:
1) If I insert a MSGBOX in callback function for Tab 1 before the
SELECT CASE statement, and then run the program, clicking on the
button in Tab 1 does not generate a call to the Tab 1 callback.
I tried integrating the DDTTab code into another program I'm working
on and the callback functions for the tabs are never called. Even if
I send a message to hTabDlg1 in an attempt to force a call. I am
pulling my hair out trying to get the controls on the tabs to resize
when the main window is resized.
Is there something missing from the example or from my understanding?
2) The TAB structure as I understand it:
In the main dialog callback for hDlg, is there any way to reference
the hTabDlg1, 2, etc. without using GLOBAL handles?
3) Should either the CONTROL SET SIZE hTab or MoveWindow hTab procedures
generate a %WM_SIZE message for the hTabDlg1,2,etc.?
------------------
Bernard Ertl
I have a few questions:
1) If I insert a MSGBOX in callback function for Tab 1 before the
SELECT CASE statement, and then run the program, clicking on the
button in Tab 1 does not generate a call to the Tab 1 callback.
I tried integrating the DDTTab code into another program I'm working
on and the callback functions for the tabs are never called. Even if
I send a message to hTabDlg1 in an attempt to force a call. I am
pulling my hair out trying to get the controls on the tabs to resize
when the main window is resized.
Is there something missing from the example or from my understanding?
2) The TAB structure as I understand it:
Code:
hDlg main/parent window hTab tab control for hDlg hTabDlg1 child window to hTab hTabDlg2 ...
the hTabDlg1, 2, etc. without using GLOBAL handles?
3) Should either the CONTROL SET SIZE hTab or MoveWindow hTab procedures
generate a %WM_SIZE message for the hTabDlg1,2,etc.?
------------------
Bernard Ertl
Comment