home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.ms-windows.programmer.misc
- Path: sparky!uunet!haven.umd.edu!darwin.sura.net!spool.mu.edu!agate!linus!progress!neil
- From: neil@progress.COM (Neil Galarneau)
- Subject: Re: WinExec return useful?
- Message-ID: <1992Sep10.180455.25745@progress.com>
- Sender: usenet@progress.com (Mr. Usenet)
- Nntp-Posting-Host: pinta
- Organization: Progress Software Corp.
- References: <dobbins.271.715550243@lan.ccit.arizona.edu>
- Distribution: usa,world
- Date: Thu, 10 Sep 1992 18:04:55 GMT
- Lines: 26
-
- dobbins@lan.ccit.arizona.edu (Gary Dobbins) writes:
-
- >When an app calls WinExec, the return value is described somewhat vaguely
- >in the SDK as a task handle, which I presume is an instance handle. (?)
-
- _Undocumented Windows_ by Schulman, Maxey, and Pietrek (an excellent book) has
- a page which discusses the return value from WinExec (the hInstance/DGROUP).
-
- >How, then, can I go about locating the hWnd for this instance's main window,
- >in order to send it messages? I've tried PostAppMessage (which accepts an
- >instance handle instead of a hWnd), with no luck.
-
- I think PostAppMessage takes an htask. The book gives a function
- hTask_from_hInstance that might do the trick.
-
- >Thanks in advance...
-
- You are welcome.
-
- > Gary L. Dobbins * University of Arizona * (602)621-6715
- > dobbins@arizona.edu * dobbins@arizvms (bitnet)
- > "Some days, you just can't get rid of a bomb..." - Batman, 1966
-
-
- Neil
- neil@progress.com
-