Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!emory!gatech!usenet.ins.cwru.edu!ysub!psuvm!cxt105
From: CXT105@psuvm.psu.edu (Christopher Tate)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Drawing direct to a dialog window...
Message-ID: <91136.152155CXT105@psuvm.psu.edu>
Date: 16 May 91 19:21:55 GMT
References: <1991May15.131300.9898@umiami.ir.miami.edu>
 <1991May16.170121.7022@oceania.UUCP>
Organization: Penn State University
Lines: 19

The cool thing about userItem's is that once you set them up (by telling
the Dialog Manager which procedure to call to draw them) you can just
forget about them completely.  The Manager will automatically call your
procedures if it becomes necessary to update the contents of the dialog
(for example, if a screen saver has erased it).

This is the recommended way of doing the bold outline around the default
button, in fact.  You create a userItem that's four pixels bigger than
the button in every direction, then use the simple FrameRoundRect()
stuff in a userItem procedure to actually draw it.  From then on, you
don't have to worry about it.  Also, the same userItem procedure can be
used by more than one dialog, whereas multiple dialogs may not be able
to (easily) share the same filterProc.

-------
Christopher Tate                      |                      etaT rehpotsirhC
Bitnet: cxt105@psuvm                  |                  mvusp@501txc :tentiB
Uucp: ...!psuvax1!psuvm.bitnet!cxt105 | 501txc!tentib.mvusp!1xavusp!... :pcuU
Internet: cxt105@psuvm.psu.edu        |        ude.usp.mvusp@501txc :tenretnI