Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!snorkelwacker.mit.edu!thunder.mcrcim.mcgill.edu!nick
From: nick@celeborn.McRCIM.McGill.EDU (Nicola Fumai)
Newsgroups: comp.os.os2.programmer
Subject: Help with WinMessageBox!
Message-ID: <1990Dec13.153322.9667@thunder.mcrcim.mcgill.edu>
Date: 13 Dec 90 15:33:22 GMT
Sender: news@thunder.mcrcim.mcgill.edu
Organization: McGill Research Centre for Intelligent Machines
Lines: 33
Originator: nick@celeborn.McRCIM.McGill.EDU
Nntp-Posting-Host: celeborn.mcrcim.mcgill.edu


Background: I am using OS/2 1.2 EE, with IBM OS/2 1.2 Toolkit, and MSC 6.00.

I was modifying the hexcalc program from chapter 14 of the Petzold
`Programming the PM' book, in order to incorporate DDE (Dynamic Data
Exchange). During processing of the DDE message `WM_DDE_INITATE' I was
using a WinMessageBox to print a message on the screen saying that the
DDE message was indeed received. The problem is that after the
WinMessageBox is created, it doesn't want to go away, and in fact
hangs the system. Pressing the OK or cancel buttons does nothing, and
even the OS window which claims that the application is not responding
to system requests...(enter to kill etc.) does nothing.

I tried using Codeview to see what was going on, but couldn't get past
the line which creates the WinMessageBox.

The manuals claim that when opening a MessageBox while a DialogBox
(ie. the hexcalc calculator) is still present, the owner should be the
Dialog's frame window. This I have done, and I have tried setting the
MessageBox parent to HWND_DESKTOP, the dialog's client window, and the
dialog's frame window, none of which work...it always hangs.

Any ideas why this is happening? Is it a 1.2 bug? feature? Or is MSC
at fault?

please email a reply...I'll post a summary if necessary.

nick
----
INET: nick@mcrcim.mcgill.edu
      nick@larry.mcrcim.mcgill.edu
UUCP: ...!mcgill-vision!nick