Posted by Grant Foraker on May 01, 2008 at 14:49:59:
In Reply to: Re: EVENTSUB question posted by Barbara Brazil on May 01, 2008 at 13:34:39:
Here's the three scenarios I've encountered over the last year.
1) Dialog that has an "Email" button. The child program has no main screens of its own. Just a series of Extended Window pop ups. Get email address. Then get "comments". I changed the "comments" pop up from Extended Windows to a milti-line text entry dialog. Everything looked good when the EXIT's collapsed back to the parent. When the "Exit" button was clicked, the dialog would clear, the QCRT screen would blank and hang. Debugger showed that the parent was still running and sitting at EVENTWAIT. Switched back to the Extended Window version and everything worked fine.
2) Dialog that creates a TXT file and copies data from a Comet keyed file. Inadvertently found this while testing. I had MAINT running on another screen and had a record in the Comet file extracted. Inside the EventHandler, while doing the data copy (in a GOSUB), the dialog program hit the E33 and invoked my special E33 display program. It's a dialog that uses SNAPSHOT to find and display all EXTRACT's in a list. After collapsing back to the parent, the parent closed the dialog and hung at the EVENTWAIT. Talked to Brian and got it figured out.
Fixed #1 and #2.
3) A non-dialog program with HYPERLINKs that ENTERs a program that has been converted from an Extended Window to a ListView dialog. The ENTER is in the mainline of the program and has nothing to do with the HYPERLINK's. Or so I thought. After returning to the parent, the HYPERLINKs wouldn't work. Debugger showed no response to clicking on the HYPERLINKs. Dawned on me that I had lost my EVENTSUB in the parent when the null EVENTSUB ran in the child.
All three turned out to be the same problem.
Each file can be a maximum of 1MB in length Uploaded files will be purged from the server on a regular basis.