Currently, the evaluation of presentation blocks such as display: [ ... ]
is lazy. However, if the inspector extension contains other code that is
outside of blocks, that code will be computed all the time because it is
considered to be presentation construction code.
Anyway, you are correct in that we need to get the inspector more bullet
proof. You will notice that this kind of errors do not happen in Spotter,
and we will apply the same rigor in the next inspector incarnation.
On Mon, Jun 29, 2015 at 7:24 PM, Nicolas Anquetil <nicolas.anquetil(a)inria.fr
In Moose, I have some problems with my sourceAnchors.
Because of these problems (bugs), sourceText does not work for these
Unfortunatelly, when I try to inspect these faulty entities in GTInspector
(for debugging) it does not work because the first thing it tries to do is
compute all panes, including the one for sourceText which is buggy :-(
- GTInspector's panes would gracefully fail and allow the inspector to be
- Compute a pane when it is visible and only at that moment (but anyway,
failing gracefully would be nice. It is always better to be graceful)
Moose-dev mailing list
"Every thing has its own flow"