Inspector Help
Usage
The visual inspector is supplied in source form in the
apps/inspector directory of the source release.
To start, first (cd "apps/inspector"), then (load "inspector.ss").
- Use (vinspect <scheme object>) to inspect an object.
- Use (vdebug) to inspect the last error continuation.
Key Bindings
Ctrl is the Control key; Alt is the Alt (or Meta) key.
| Key | Binding |
| Q, q | Quit |
| F | Forward |
| B | Backward |
| space, page down | Forward page |
| backspace, page up | Backward page |
| Ctrl-n, j | Forward line |
| Ctrl-p, k | Backward line |
| < | Go to top |
| > | Go to end |
Button Actions
| Button | Action |
| File -> Quit | destroy current inspector only |
| File -> Spawn | create new inspector viewing only the current object |
| Go | object history |
| Font... | font dialog |
| < | previous object |
| > | next object |
| R | refresh (reload view in case object is side-effected) |
Bugs
- A null embedded in a string will
confuse string inspection quite
a bit.
- The keys are somewhat unintuitive.
- Ruthlessly stealing Netscape's interface
Features
- Very few side-effects.
- Using an xy-output-string, which
keeps info about xy position as well
as offset. This needs
set-port-output-buffer!, I think.
- Ruthlessly stealing Netscape's
interface.
Todo
- circular structures
- ports
- named taggable objects
- sliders for length and level
- perhaps reorganize the creation of
inspect-windows so that they
keep their length and level better,
as well as keeping their graph-envs
and fonts (done now with
parameterize).