home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.ms-windows.programmer.misc
- From: chris@chrism.demon.co.uk (Chris Marriott)
- Path: sparky!uunet!pipex!demon!chrism.demon.co.uk!chris
- Subject: Re: Executing Windows or DOS application from Windows
- Distribution: world
- References: <Bzw446.AEr@pcuf.fi>
- Organization: None
- Reply-To: chris@chrism.demon.co.uk
- X-Mailer: Simple NEWS 1.90 (ka9q DIS 1.19)
- Lines: 28
- Date: Mon, 28 Dec 1992 21:07:43 +0000
- Message-ID: <725576863snz@chrism.demon.co.uk>
- Sender: usenet@demon.co.uk
-
- In article <Bzw446.AEr@pcuf.fi> turre@pcuf.fi writes:
-
- >I am writing an application which should first unpack .ZIP's and later on
- >call an editor. Calling with WinExec is not difficult, but Windows keeps
- >executing my application while it should wait DOS or the editor to finish.
- >I can do a while loop with FindWindow, but problem is what to do inside
- >the loop. If I use GetMessage user can access my apps menus & buttons whichh
- >should not be allowed. DisableWindow will not help because user will not
- >get back to the application if he, while in editor, switches task.
- >
- >So I would like to wait for the tasks to finish with doing nothing in my
- >own app still allowing other applications to work. Help is appreciated in
- >both DOS case and Windows case.
- >
-
- Why not simply set a "DOS Application is running" flag in your program at
- the time you start the program running, then ignore any WM_COMMAND messages
- you receive if the flag is set to "TRUE". That's what I'd do, anyway.
-
- Chris
- --
- --------------------------------------------------------------------------
- | Chris Marriott | chris@chrism.demon.co.uk |
- | Warrington, UK | BIX: cmarriott |
- | (Still awaiting inspiration | CIX: cmarriott |
- | for a witty .sig .... ) | CompuServe: 100113,1140 |
- --------------------------------------------------------------------------
-
-