Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!bloom-beacon!ATHENA.MIT.EDU!swick
From: swick@ATHENA.MIT.EDU (Ralph R. Swick)
Newsgroups: comp.windows.x
Subject: Re: Calling callbacks from a widget's set_values procedure
Message-ID: <8906051259.AA07756@LYRE.MIT.EDU>
Date: 5 Jun 89 12:59:26 GMT
References: <5107@pt.cs.cmu.edu>
Sender: daemon@bloom-beacon.MIT.EDU
Organization: DEC/MIT Project Athena
Lines: 10

> Is there anything wrong with having a widget's SetValues() procedure
> call some callbacks as a result of a state change? 

Nope, not at all.  You will have to be careful, however, to make sure
the widget hierarchy is in a consistent state when you execute the
callbacks, or carefully document the environment that the callback
will see.  For example, if you follow the recommended geometry
management scheme the widget's geometry fields are not accurate
until after all the set_values (and the final set_values_almost)
methods have completed.