CLIM 1.1 erase-output-record ?

• To: jmorrill@BBN.COM
• Subject: CLIM 1.1 erase-output-record ?
• From: John Aspinall <jga@harlequin.com>
• Date: Thu, 30 Jun 1994 11:31:51 -0400
• Cc: everett@wintermute.ils.nwu.edu, clim@BBN.COM
• In-Reply-To: Jeff Morrill's message of Thu, 30 Jun 1994 10:51:35 -0400 <145.772987895@ziggy.bbn.com>

   In-Reply-To: John Everett's message of Thu, 30 Jun 1994 09:28:17.
		<9406301428.AA18673@wintermute.ils.nwu.edu> 
   Reply-To: jmorrill@BBN.COM
   Date: Thu, 30 Jun 1994 10:51:35 -0400
   From: Jeff Morrill <jmorrill@BBN.COM>

   This is indeed a FAQ.  You are getting bitten by the bug in
   coordinate sorted sets.  I don't know if there are any other
   types of output records in clim 1.

   jeff morrill

But it's not the same bug as Marilyn Bunzo's bug.  In Everett's case,
he's looking up a known-to-be-present output-record.  There *is* a fix
for Everett's bug - I was still at 'Bolics when Scott and I put it in,
and it's in the CLIM 2 sources.

Perhaps someone has this patch stashed somewhere.  If dredging up the
CLIM 1 sources wasn't slightly harder than getting universal
health-care coverage, I'd mail it to you now.

John

• CLIM 1.1 erase-output-record ?
• From: David Gadbois <gadbois@mcc.com>

• Re: CLIM 1.1 erase-output-record ?
• From: Jeff Morrill <jmorrill@BBN.COM>

• Prev: Re: CLIM 1.1 erase-output-record ?
• Next: Passing user-defined arguments to presentation methods
• Index: CLIM Mailing list (1-Jun-94 to 30-Jun-95)
• Thread: CLIM Mailing list Index (1-Jun-94 to 30-Jun-95)