Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!sdd.hp.com!mips!sgi!shinobu!fido.wpd.sgi.com!marktwain.rad.sgi.com!linton
From: linton@marktwain.rad.sgi.com (Mark Linton)
Newsgroups: comp.windows.interviews
Subject: Re: Glyphs and Unidraw
Message-ID: <1991May16.162033.22547@fido.wpd.sgi.com>
Date: 16 May 91 16:20:33 GMT
References: <1991May15.184124.13302@colorado.edu>
Sender: news@fido.wpd.sgi.com (Usenet News Admin)
Reply-To: linton@marktwain.rad.sgi.com (Mark Linton)
Organization: sgi
Lines: 11

In article <1991May15.184124.13302@colorado.edu>, grunwald@foobar.colorado.edu (Dirk Grunwald) writes:
|> Btw, are Glyphs the appropriate level for constructing small
|> widget-like things in 3.0? I don't care about backwards compatibility;
|> however, I don't see how Glyphs & Unidraw interact, and I see several
|> problems that indicate I'm missing something (like, if a glyph updates
|> a value asynchronously, how do you tell all Canvas's using that Glyph
|> that this has occured?)

Unidraw and glyphs will be integrated in 3.1.  Use a Patch (MonoGlyph subclass)
to wrap around a glyph tree that you want to update.  Patches store a pointer
to the canvas and can damage it when updating.