Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!caen!ox.com!heifetz!tbomb!time
From: time@ice.com (Tim Endres)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Modeless Dialogs
Date: Fri, 5 Apr 91 09:49:42 EST
Organization: ICE Engineering, Inc.
Message-ID: <1CE00001.cbpilg0@tbomb.ice.com>
Reply-To: time@ice.com
X-Mailer: uAccess - Mac Release: 1.1.b1
Lines: 33


In article <1991Apr5.081306.511@leland.Stanford.EDU>, calvin@portia.stanford.edu (Peter Chang) writes:
> Hello Netters,
> 
> 	I am writing a program that needs some modeless dialogs, and
> I have  few questions on how to implement them. I'm learning
> how to use the Think Class Library at the same time, so some of
> my ideas may seem odd.
> 
> 	1.	It seems to me that a modeless dialog is just a window with
> some buttons, text boxes, and other things. Because it seems
> this way to me, would it be advisable to implement it by making
> a window with the requisite components built in?

Apple has recommended from the beginning that dialogs only be used
where creating a window would entail much more work. And they have
also recommended you limit dialogs to a small number of items. 
If you implement this as a window, you will enjoy some freedom and
benefits you would not as a dialog, but you will have to do a little
more work.

> 	2. If part 1 was answered with an affirmative, would the best
> way to implement this be to override the Pane class with some 
> Buttons and other objects thrown on when I need them?

I am not sure how MacAPP implements its control objects within Panes
of windows, but it sounds right.

-------------------------------------------------------------
Tim Endres                |  time@ice.com
ICE Engineering           |  uupsi!ice.com!time
8840 Main Street          |  Voice            FAX
Whitmore Lake MI. 48189   |  (313) 449 8288   (313) 449 9208