Reworked and moved TP guide #103
Conversation
|
|
||
| The **Next Primitive** icon is always present in the tracer. The new **<TP>** command lets you open a tracer on an expression typed directly in the session that previously could not be traced into. | ||
|
|
||
| ## Anatomy of the TP Interface |
There was a problem hiding this comment.
The "Anatomy of a TP Interface" section should be renamed and moved to be a sub-section of the Tracer section; it is not specific to tracing primitives (even though it happened to be implemented at the same time); the images are not necessary and add a maintenance overhead. The "Aspect Panes" section is specific to tracing primitives and should remain.
Suggested rewrite:
Display
There are three layout modes; these can be selected from the Layout menu:
- Classic – the Tracer is detached from the Session window and can be positioned as required.
- Debugger at the bottom – the Tracer is positioned beneath the Editor within the Session window. This is the default setting
- Debugger on the left – the Tracer is to the left of the Editor within the Session window.
In all three modes, there are two docked, but minimised, panes named Left Argument and Right Argument. These automatically expand as you trace through an expression.
There was a problem hiding this comment.
I will leave this for now until we have clarity on the old/new classic modes.
There was a problem hiding this comment.
Image is unnecessary and should be removed
There was a problem hiding this comment.
Image is unnecessary and should be removed
There was a problem hiding this comment.
Image is unnecessary and should be removed
|
|
||
| ### Aspect Panes | ||
|
|
||
| There are several more aspects of an expression that can be inspected in TP mode beyond the left and right arguments. These are available under the **Windows** menu when in tracing mode. |
There was a problem hiding this comment.
Suggested rewrite:
When tracing primitives, the Windows menu in the Tracer offers additional panes beyond the default ones for left and right arguments. These can be are divided into two sections; items 1-4 apply to the current function, and items 5-9 apply to the previously-executed function. They are:
There was a problem hiding this comment.
I think this documents the effect (additional panes) instead of the purpose (further inspection options). How about
When tracing primitives, there are several more aspects of an expression that can be inspected beyond the default ones for left and right arguments, available under the Windows menu in the Tracer. These are divided into two sections; items 1-4 apply to the current function, and items 5-9 apply to the previously-executed function. They are:
There was a problem hiding this comment.
When tracing primitives, there are several more aspects of an expression that can be inspected beyond the default ones for left and right arguments. These are available under the Windows menu in the Tracer, where they are divided into two sections; items 1-4 apply to the current function, and items 5-9 apply to the previously-executed function. They are:
|
Note: the other changes needed to this document have not been included in this Pull Request (see Mantis issue for what they are). |
|
Should links like these be documentation/windows-ui-guide/docs/tracer/index.md Lines 49 to 53 in 208794f |
|
@MaxCan-Code thank you for spotting that; should be fixed in the next update I push. |
| <h2 class="example">Example</h2> | ||
| In a Session, enter the expression `(+/÷≢)⍳10` and start tracing primitives. | ||
|
|
||
|  |
There was a problem hiding this comment.
Should ../../img be ../img?
|  | |
|  |
References #82