RE: DisplayImpl Simplified: addReferences

• To: "'From: Bill Hibbard <hibbard@xxxxxxxxxxxxxxxxx>'" <billh@xxxxxxxxxxxxx>, "Simons, Randall W" <rsimons@xxxxxxxxxx>
• Subject: RE: DisplayImpl Simplified: addReferences
• From: "Simons, Randall W" <rsimons@xxxxxxxxxx>
• Date: Fri, 25 Jan 2002 17:35:55 -0700

Thank you!!!  That's the magical incantation I was looking for.  Putting
disableAction() and enableAction() around all my addReferences() runs just
as fast as my previous kludge, and feels much better.  That's a good way to
finish the week.

> -----Original Message-----
> From: From: Bill Hibbard <hibbard@xxxxxxxxxxxxxxxxx>
> [mailto:billh@xxxxxxxxxxxxx]
> Sent: Friday, January 25, 2002 3:21 PM
> 
> The big performance gain you see in removing the use
> of mapslock in addReferences() might also be acheivable
> by enclosing the sequence of operations on your
> DisplayImpl between calls to display.disableAction()
> and display.enableAction(). Probably your first
> addReferences() triggers a call to doAction(), which
> locks out later addReferences() calls. The disableAction()
> will prevent the doAction() call until the enableAction().

Randall W. Simons
Sandia National Laboratories