home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.lang.pascal
- Path: sparky!uunet!comp.vuw.ac.nz!cc-server4.massey.ac.nz!pnv.palm.cri.nz!hrpdko
- From: hrpdko@pnv.palm.cri.nz (Dale K. Ogilvie)
- Subject: Re: Constructing TDialogs with only a Handle
- Message-ID: <hrpdko.62@pnv.palm.cri.nz>
- Sender: news@massey.ac.nz (USENET News System)
- Organization: DSIR, Palmerston North, New Zealand
- References: <02oai4.$=2@cat.de> <1993Jan27.095112.23954@sol.ctr.columbia.edu>
- Date: Thu, 28 Jan 93 01:32:35 GMT
- Lines: 22
-
- In article <1993Jan27.095112.23954@sol.ctr.columbia.edu> gtd543a@sol.crt.columbia.edu (death) writes:
-
- >Stefan Ludwig (ludwig@cat.de) wrote:
- >: TDialog-Constructor Init takes a PWindowsObject as an argument. Id like to
- >: construct one without the parent beeing a PWindowsObject. The situation: I
- >: wrote a DLL which is called from within a third party program (which I dont
- >: have the source for). I can get the handle of the applications main window
- >: in the DLL's code. Now I would like to generate Dialogs which are modal and
- >: have the applications main window as a parent.
-
- >Unfortunately, according to Borland (I wanted to do this also) you
- >cannot use OWL in a DLL, which is a real bummer.
- >--
- >Death: the high price of living
- >========================================================================
- >Disclaimer: I am not bubba.
-
- I second this, I couldn't get OWL working in a DLL either. Anyone have a
- different view?
-
- Dale Ogilvie
-
-