Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!magnus.acs.ohio-state.edu!tut.cis.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!rutgers!rochester!pt.cs.cmu.edu!o.gp.cs.cmu.edu!andrew.cmu.edu!dl2p+
From: dl2p+@andrew.cmu.edu (Douglas Allen Luce)
Newsgroups: comp.lang.pascal
Subject: Making modal modeless (TVision question)
Message-ID: <QbxJI3a00XQC9=_HVS@andrew.cmu.edu>
Date: 31 Mar 91 03:18:27 GMT
Organization: Class of '91, Carnegie Mellon, Pittsburgh, PA
Lines: 35

Hi,

I may just be up late, but I cannot seem to find an adequate
solution to my quandary:

Within a modal dialog box called through Desktop^.ExecView, I have an
option which is supposed to create a window and place it on the
desktop, and then make it active.

When ExecView is called, the state of the desktop is saved.  After
I've placed the window in the DeskTop (through a call to
DeskTop^.Insert from the dialog box), the EndModal procedure is
called.  Within this procedure, the previous state is saved, and my
window cannot come up selected.  

Apparently, any messing with the DeskTop is erased after the EndModal
is finished, and I cannot kludge something by passing back a command
to the call of DeskTop^.ExecView to select the window now down,
because the DeskTop^.Current is empty, and the desktop doesn't think
there's anything out there!

It appears that perhaps the only thing I can do is to send an "Insert
Window" command all the way out of the modal dialog chain back to the
ExecView calling procedure, and then having it handle inserting the
window.  Since the window relys heavily on the context of the dialog
boxes, doing this would be hacky at best.

I must be missing something obvious; this seems like such a useful
thing to do!

Can anyone wake me up?

Douglas Luce
Chemical Engineering
Carnegie Mellon