Newsgroups: rec.arts.int-fiction
Path: news.duke.edu!newsgate.duke.edu!nntp-out.monmouth.com!newspeer.monmouth.com!news.maxwell.syr.edu!news-out.uswest.net!uunet!chi.uu.net!arb.uu.net!ffx.uu.net!world!buzzard
From: buzzard@world.std.com (Sean T Barrett)
Subject: Re: [inform] conversation menus
Message-ID: <G6AFor.FGq@world.std.com>
Date: Thu, 28 Dec 2000 17:10:03 GMT
References: <slrn94ithq.12i.cerutti@localhost.localdomain> <20001227113214.10677.00000020@ng-cl1.aol.com> <92dan7$4bs$1@news5.svr.pol.co.uk> <G69B9I.CDD@world.std.com>
Organization: The World Public Access UNIX, Brookline, MA
Lines: 19
Xref: news.duke.edu rec.arts.int-fiction:81717

Sean Barrett wrote:
>so you have to refine it to
>
>   process previous command
>   get user input
>   if it's UNDO, process it
>   save_undo
>   if return code indicates we just restored, jump back to 'get user input'
>   process the current command

Now when you try to stick this into a conversation system,
you have to have two copies of this code (one for regular prompts
and one for the conversation prompts), and one of them might be
restoring to the save_undo from the OTHER version of the code,
and I think that's all ok and it'll just work, but I'm not positive
'cause I've never tried it nor have I thought it through as
carefully as the above.

SeanB
