We have developed a libray that bridges our old DOS screen handler and Win95 API. Our library creates Win95 windows that represent the old DOS versions of the screens. Because of the way the DOS screen handler is constructed, it is necessary for our library to read the DOS screen layout, create the win95 parent window, and create the appropriate edit controls on the parent window. In some cases we also use combo controls instead of edit controls. Things are working except for two nagging problems that we can't seem to pin down:
1) When tabbing between edit fields we always trigger a beep (or the Windows default sound). We have been unable to determine what the trigger actually is. It seems to occur outside of our code. Our programmer has traced through the edit control handler function (ours) and determined that the beep occurs sometime after that handler function finishes and returns control back to Windows. Any idea what could cause this?
2) We seem to be unable to trap many of the messages we need to trap in the combo box control. Our message handler does get some messages for the combo box controls, but never receives the messages we really want to handle (like key down). THe creation of the combo box seems to be done correctly, yet we are cut off from receiving messages. Any ideas?