Re: [Tads3] Hints Suggestion

["Eric Eve" <eric.eve@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>]

Mike Roberts wrote:

> The when-known properties definitely seem worthwhile to add. I'm not sure
if when-moved
> will come up so often, but I'd be happy to add it if other people think
it's worth
> adding - any opinions?

Fair enough; I agree that if no one else uses when-moved much it's not worth
adding to the library (it proved easy enough to implement as a custom
property in any case). I did check to see whether I'd been simply using it
as a way to get round the problem with seen I raised in another post, but it
looks to me as if on most of the occasions I've used it, when-moved is
probably the better condition to test (usually because I've used moveInto
either to represent an NPC giving the PC something or the PC finding
something hidden in a non-obvious way).

> Would it be useful to add openWhen and closeWhen methods that encapsulate
the full set
> of openWhenXxx checks? These would be almost the same as
openWhenTrue/closeWhenTrue,
> but the idea here is that they're specifically for the game's use in
'modify Goal'
> rather than something you'd define per instance. This would make it a lot
easier for a
> game to add something like openWhenMoved when that came up a lot in a
specific game,
> because you'd be able to add the condition with a simple 'modify':

This would be nice; of course one can simply modify goal with a custom
updateContents() method now (which is what I did and which looks pretty
similar to the code in your suggestion), but it would be a bit easier to
modify the proposed openWhen & closeWhen methods.

-- Eric