Inspect often fails
For example... myVar inspect.
- Calling inspect from a system without gst-blox doesn't always work. Sometimes it stack dumps.
- Calling inspect from a system with gst-blox will try to open a graphical "inspect" window. Sometimes this window shows in the operating system but no output appears in it and then after about 30 secs it disappears. Sometimes GST gets in a loop generating inspect windows.
System documentation is...
inspect Print all the instance variables of the receiver on the Transcript
This doesn't imply that an X Window will get opened.
The "inspect" method is useful for debugging and when using a class that someone else has written to see what objects it returns. Please remove the "Windowing link" so that if a script is _not_ running inside gst-blox, then GST will dump output to Transcript and not try to open an XWindow.
Can you provide a simple way to reproduce this?
the root problem was the last one (deadlock if the transcript raises an exception), which I had split out to issue 283.