[kepler-dev] problems with annotations

Edward A. Lee eal at eecs.berkeley.edu
Wed Oct 26 13:01:35 PDT 2005


At 08:01 AM 10/26/2005 -0700, Christopher Brooks wrote:
>Your design of using EmptyChangeRequest seems reasonable, though
>it seems to point out a bug in the Ptolemy code.

I don't think it's a bug in the Ptolemy code.
The reason that EmptyChangeRequest works is that after
any change request, the model gets redrawn.  This is
a very brute-force way to react to change requests,
and in fact is very costly (even changes that have no
visible side effects will trigger a redraw).
Thus, the real problem is long term: If we fix Ptolemy II
so that redraws occur only when necessary, then the
EmtpyChangeRequest will no longer do what you want...

Edward



------------
Edward A. Lee
Professor, Chair of the EE Division, Associate Chair of EECS
231 Cory Hall, UC Berkeley, Berkeley, CA 94720
phone: 510-642-0253 or 510-642-0455, fax: 510-642-2845
eal at eecs.Berkeley.EDU, http://ptolemy.eecs.berkeley.edu/~eal  



More information about the Kepler-dev mailing list