Re: Prompts

• Date: Tue, 5 Mar 1996 06:34:25 PST
• From:
  Kipp the Kidd <mcmudge@mailbox.syr.edu>
• cc: siman@ihug.co.nz (Ian Macintosh), moo-cows.PARC@xerox.com
• Content-Type: text/plain; charset="us-ascii"

At 01:57 AM 3/5/96 PST, Ahn Jin-su wrote:
>  I wrote a patch for this for 1.7.8p4. I ported it to 1.8.0alphas, but not
>for 1.8.0betas for yet. I first wrote it like Ian's, then modified it to
>track down suspend()ed or read()ing commands, and call #0:do_prompt()
>after the task completely ended. Then I added a built-in and $server_option
>to control its action. (the server may or may not call #0:do_prompt() when
>a *command* task suspends, and don't call #0:do_prompt() while read()ing)
>It doesn't call #0:do_prompt() for fork()ed tasks. (seems natural to me)
>  However, it had some subtle bugs, and I couldn't wipe them out. I
>modified the code heavily (200+ lines added) and thinks it needs some
>refining, but I haven't got enough time for it. I'm planning to finish it
>after final 1.8.0 release. Unfortunately, there may be little time to
>concentrate on this until summer......
>  If anyone interested, I could send the patch or make it available by
>ftp, maybe...

There are still a few problems with this method of displaying prompts.  What
if a command suspends, but does not notify the player after the suspend?
...like a spell, it would be casted, suspend, wear off, and might not tell
the player it has worn off, but the suspend finished.  They get an extra
prompt... bad.

- Kipp
-----BEGIN GEEK CODE BLOCK-----
GCS/CC d- s+:- a16 C++ UL++++ P+ L++ E-? W+ !N--@ !o-- K->K++++++
w++(--) O- M-- V--? PS++(+) PE(--) Y+ PGP-? t+ 5(+) X++ R+++(*)
!tv b+ DI++++ D++++ G e* h!()(*) r+ !y+
------END GEEK CODE BLOCK------
-----BEGIN NOT SO GEEKY BLOCK-----
MOO projects:
  RPG Minimal.db:  paradigm.microwave.com 5000
  MOO2000:         moo.microwave.com 2000
  MundoHispano:    europa.syr.edu 8888
------END NOT SO GEEKY BLOCK------

• Prev: Re: Prompts
• Next: Re: Prompts
• Index: MOO-cows
• Thread: MOO-cows