ifhub/inform7
1
0
Fork 0
mirror of https://github.com/ganelson/inform.git synced 2024-06-28 21:14:57 +03:00
Code Issues Projects Releases Wiki Activity

initial commit of showtree

Browse source
This commit is contained in:
Zed Lopez 2023-07-23 23:14:54 -07:00
parent 2c84a758d1
commit 036034955d
4 changed files with 50 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
inform7/Internal/Inter/WorldModelKit/Sections/Tests.i6t
View file

@ -481,7 +481,7 @@ of 0 (off, the default) to 5.
[ TraceOffSub; parser_trace=0; say__p = 1; "Trace off."; ];
@h Tree Command.
TREE prints out the I6 object tree, though this is not always very helpful
SHOWTREE prints out the I6 object tree, though this is not always very helpful
in I7 terms. It should arguably be withdrawn, but doesn't seem to do any harm.
=
@ -589,7 +589,7 @@ Verb meta 'trace'
* number -> TraceLevel
* 'on' -> TraceOn
* 'off' -> TraceOff;
Verb meta 'tree'
Verb meta 'showtree'
* -> XTree
* scope=testcommandnoun -> XTree;
#Ifdef TARGET_GLULX;

6
inform7/Tests/Test Cases/Showtree.txt Normal file
View file

@ -0,0 +1,6 @@
Lab is a room.
The red tree is in the Lab.
The red envelope is in the Lab.
Test me with "x red / tree / showtree".

40
inform7/Tests/Test Cases/_Results_Ideal/Showtree.txt Normal file
View file

@ -0,0 +1,40 @@
Lab
Welcome
An Interactive Fiction
Release 1 / Serial number 160428 / Inform 7 v10.2.0 / D
Lab
You can see a red tree and a red envelope here.
> > Lab
(Testing.)
>[1] x red
Which do you mean, the red tree or the red envelope?
>[2] tree
You see nothing special about the red tree.
>[3] showtree
(Compass object) (22)
the north
the northeast
the northwest
the south
the southeast
the southwest
the east
the west
the up
the down
the inside
the outside
(thedark object) (23)
(VPH_25) (24)
(VPH_3) (25)
Lab (39)
yourself
a red tree
a red envelope
> >

4
resources/Documentation/Writing with Inform.txt
View file

@ -16198,7 +16198,7 @@ If, however, we want a rapid overview of all the responses provided by a given e
^^{ABSTRACT+testcmd+} ^^{testing commands: >ABSTRACT}
^^{GONEAR+testcmd+} ^^{testing commands: >GONEAR}
^^{>VERIFY}
^^{TREE+testcmd+} ^^{testing commands: >TREE}
^^{SHOWTREE+testcmd+} ^^{testing commands: >SHOWTREE}
^^{SCOPE+testcmd+} ^^{testing commands: >SCOPE}
^^{SHOWHEAP+testcmd+} ^^{testing commands: >SHOWHEAP}
^^{SHOWVERB+testcmd+} ^^{testing commands: >SHOWVERB}
@ -16248,7 +16248,7 @@ As a debugging command, this isn't protected in the ways that commands usually a
VERIFY checks that the story file is intact rather than damaged, but it is hard to think of an occasion when this would be likely to arise within the Inform application. The command is a holdover from a time when data transfer was much slower and more error-prone, and it was plausible to have a story file of just a few hundred KB corrupted during transmission.
TREE creates a list of object containment. It is similar to SHOWME, but less elegant and thorough.
SHOWTREE creates a list of object containment. It is similar to SHOWME, but less elegant and thorough.
SCOPE lists the objects that are currently in scope for the player, which is to say, things that could be referred to when we're typing a typical command. Thus: