MDI Parent and child (OpenInsight Specific)
At 12 JUN 2000 05:06:35PM Andy Becker wrote:
In our system we start with an MDI Parent screen which loads the Data Base Applications screen (DB APP). The DB APP screen has 20 invisible check boxes. When created, the logic accesses the SYSAPPS table and determines, by attempting to read a given file in the various directories, if the user has access to this system. If there is no access, the next system is checked. Only those systems to which the user has access to is displayed on the DB APP screen.
When the user selects an application, the main menu for that system is displayed and the various options are available.
The above is no problem.
The problem ? When the user is finished with a particular system and exits that system, we want to have the DB APP screen displayed with the systems they have access to. Every time we exit the system to return to this screen (DB APP) we only get the MDI Parent screen. Any ideas what we can do to accomplish this?
At 13 JUN 2000 06:35AM Oystein Reigem wrote:
Andy,
One piece in the puzzle could be to have something - e.g an OMNIEVENT handler - on the frame that checks if there are any child windows running. For the check use
allWindowsInSystem=Utility( 'OBJECTLIST', '', 'WINDOW' )and see if allWindowsInSystem contains the name of any child window (you know their names). Or perhaps just look for the presence of any other window than the frame itself (this will work as long as there aren't other app top level windows running). If no child windows are running the handler should launch the DB APP child.
The other piece must be something that triggers the first handler. One possibility is a TIMER or IDLEPROC handler (which I have limited knowledge about) on the frame.
Another possibility for this second piece is some CLOSE handler(s) for the child windows. Either have a CLOSE handler for each single child, or one promoted CLOSE for all windows. Each time a child (or any window) is CLOSEd, tell the first handler to check (i.e, send a suitable OMNIEVENT to the frame). Btw - there's one thing I'm not certain about, and that's if the child really is closed by the time the frame gets the message. But there must be a workaround for that.
- Oystein -