[1339] in Coldmud discussion meeting

root meeting help first first in chain previous in chain previous next next in chain last in chain last

RE: [COLD] Exit announcements (anomaly?)

daemon@ATHENA.MIT.EDU (Fri Aug 22 00:37:04 1997 )

From: "Luther, Clay" <clay@selsius.com>
To: "'Brandon Gillespie'" <brandon@roguetrader.com>,
        Chris Williams
Cc: "Luther, Clay" <clay@selsius.com>,
Date: Thu, 21 Aug 1997 23:14:23 -0500

See below...

> -----Original Message-----
> From:	Brandon Gillespie [SMTP:brandon@roguetrader.com]
> Sent:	Thursday, August 21, 1997 9:24 PM
> To:	Chris Williams
> Cc:	Luther, Clay; 'coldstuff@cold.org'
> Subject:	Re: [COLD] Exit announcements (anomaly?)
> And like I said, I just forgot to consider it would be out of order.
> This
> is fixed by simply excluding the user from the dest announce and
> explicitly sending them the message first, ala:
>     user.tell(message);
>     user.move_to(dest);
>     dest.announce(message, user);
>     source.announce(message);
> And everything works as one would expect it :)
> -Brandon Gillespie
> [Clay Luther]  
> Does it?  I attempted to apply this fix to $exit.invoke(), but, even
> though I can list the changes, it appears that the exits I've created
> aren't calling $exit.invoke() at all.  In fact,
> I went so far as to put debug messages like s.tell("HIYA!") in the
> code.  These don't show up. Am I misunderstanding how Cold objects
> call methods on their parents?
> Here's the code as I changed it (from $exit.invoke()):
>   // Brian's fix for the out of order exit announcements
>   m = .eval_message("invoke", $exit, .exit_msg_vars(s));
>   s.tell(m);
>   s.move_to(dest);
>   dest.announce(m, s);
>   source.announce(m);