home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.mac.programmer
- Path: sparky!uunet!usc!sdd.hp.com!mips!darwin.sura.net!haven.umd.edu!ni.umd.edu!zben-mac-ii.umd.edu!user
- From: zben@ni.umd.edu (Charles B. Cranston)
- Subject: Re: InitDialogs [Q]
- Message-ID: <zben-200892152911@zben-mac-ii.umd.edu>
- Followup-To: comp.sys.mac.programmer
- Sender: usenet@ni.umd.edu (USENET News System)
- Nntp-Posting-Host: zben-mac-ii.umd.edu
- Organization: UM Home for the Terminally Analytical
- References: <9208040003.AA02657@ucbvax.Berkeley.EDU> <71422@apple.Apple.COM>
- Date: Thu, 20 Aug 1992 19:44:06 GMT
- Lines: 19
-
- > robert_hess@macweek.ziff.com ("Robert Hess") writes:
- > ... What's wrong with calling InitDialogs from within an INIT? ...
-
- In article <71422@apple.Apple.COM>, stevec@Apple.COM (Steve Christensen)
- wrote:
- > ... Typically you need to call the following routines first:
- > InitGraf (QuickDraw)
- > InitFonts (Font Manager)
- > InitWindows (Window Manager)
- > TEInit (TextEdit)
- > and -then-
- > InitDialogs (Dialog Manager)
-
- The InitWindows has the cosmetically ugly side effect of
- repainting the desktop, wiping out the "icon parade" of all
- the other inits that have run before this one. Does anybody
- have a clean work-around around for this?
-
- zben@ni.umd.edu -KA3ZDF
-