I have a question that maybe wiser/more experience Win32 people can
A project I'm working on requires a modeless window with a tab control
to be implemented as a class (without using MFC) so that it can just
be Create()d, pages (also classes with event handlers) can be Add()ed
to it and it destroys itself on exiting. The following is the way I
thought of doing it.
- Since doing it any other way seems to involve adding message-pump
hooks ( like IsDialogMessage() ), which I cannot do, I am implementing
it as a modeless window with its own thread and message pump. This
effectively restricts contact to the moment of creation.
- The modeless window (of dialog class) has a child tab control dialog
and three children buttons (OK, Cancel, Apply).
- At the time of adding pages, tabs are added to the tab control with
their corresponding dialogs (the pages), which are dialog resources
(with WM_CHILD set and no border/caption) created with CreateDialog()
as children of the tab control.
- I handle making the pages visible/invisible, as well as redirecting
events to the corresponding page classes.
The problem is this:
I cannot, for the life of me, enable tab navigation of controls
between the tab control's tabs and the controls on the pages inside
the tab control display area.
I've tried the knowledge database, asked around, tried different
window styles, etc. to no avail. I just cannot tab from the tabs to
the controls inside the display area. A guy I wrote to told me
there's just no way of doing this, the only way is to use a property
Any help would be appreciated!
P.S. In my thread's message pump I do include IsDialogMessage()...