home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!olivea!hal.com!decwrl!pa.dec.com!nntpd2.cxo.dec.com!nntpd.lkg.dec.com!engage.pko.dec.com!tfh.enet.dec.com!marshall
- From: marshall@tfh.enet.dec.com (Hunting the Snark)
- Newsgroups: comp.os.ms-windows.programmer.tools
- Subject: Re: Using Borland Custom Control Library
- Message-ID: <1992Aug21.055145.20718@engage.pko.dec.com>
- Date: 21 Aug 92 06:38:42 GMT
- Sender: newsdaemon@engage.pko.dec.com (USENET News Daemon)
- Organization: Digital Equipment Corporation
- Lines: 37
-
-
- In article <ins434u.713663367@aurora.cc.monash.edu.au>, ins434u@aurora.cc.monash.edu.au (D. May) writes...
- >
- >I have this problem with TPW. I am learning how to do TPW's menus, dialogs,
- >etc with Resource Workshop - and am joggin through it with Neil Rubenking's
- >Turbo Pascal book.
-
- (aside) I really like Tom Swan's book, but haven't read Rubenking.
-
- >
- >I always thought that Resource Workshop was pretty cool because you could
- >access Borland's nice-looking dialogs, etc. However, I have just found out
- >(from reading Rubenking's book) that unless BWCC.DLL is loaded (i.e. if you're
- >doing something like running Resource Workshop) your nice custom control
- >dialogs don't load up properly.
- >
- >I tried it this morning and he was right. But he says, instead of using
- >WObjects and StdDlgs, use the units WObjectB and StdDlgB - wait a minute...
-
- I believe that you should have them. They came with TPW1.0 and were dropped
- in 1.5 in favor of BWCC.TPU
-
- In the mean time if you just want your dialogs to have the "Borland Look", just
- put a LoadLibrary('BWCC.DLL') command in your app like this:
-
- begin
- LoadLibrary('BWCC.DLL');
- TMyApp.Init('MyApp');
- TMyApp.Run;
- TMyApp.Done;
- end
-
- What 'using' the units will buy you is "the look" in the more mundane
- MessageBox and other Windows-created dialogs.
-
-
- Sm
-