Re: Strange (to me) behavior with define-command

• To: coulman@skdad.usask.ca
• Subject: Re: Strange (to me) behavior with define-command
• From: Jeff Close <jclose@chesapeake.ads.com>
• Date: Mon, 24 Aug 92 10:39:13 EDT
• Cc: clim@BBN.COM
• In-Reply-To: Randy Coulman's message of Sat, 22 Aug 92 21:45:35 CST <9208230345.AA13889@skdad.USask.ca>
• Reply-To: jclose@ads.com

   ...
   If an instance of class B is presented, then which command is accessible by
   the :edit gesture depends on the order that the commands are defined.  If
   edit-A is defined first, then edit-B is never accessible.  If edit-B is
   defined first, then everything is OK.  

   It doesn't explicitly say so in the documentation, but I would (and did)
   assume that the translator for the most specific presentation type would be
   accessible before any others.  I can always explicitly define the
   translators manually with the right priority values, or use a tester for
   edit-A to make sure that the objects are not B's, but I think this
   should be handled automatically.  Comments?

Randy,

I had exactly the same behavior in some of my code.  I had explicitly
defined presentation translators, though.  I didn't ask about it at
the time, and I solved it by doing what you described -- using type
testers in the translators.   Anyone have a  comment about why this is
necessary? 

jffry

• Re: Strange (to me) behavior with define-command
• From: Scott McKay <SWM@stony-brook.scrc.symbolics.com>

• Strange (to me) behavior with define-command
• From: Randy Coulman <coulman@skdad.usask.ca>

• Prev: UUCP Accounting for clim@nrbmi2.ia.nrb.be
• Next: clim 2.0 color dialog code
• Index: CLIM Mailing list (1-Jan-92 to 31-Aug-92)
• Thread: CLIM Mailing list Index (1-Jan-92 to 31-Aug-92)