Run your code to see the function-call tape.
For Python, calls are recorded automatically (use Step Run on the Inspector toolbar).
For JavaScript or Java (Processing), you have to record the markers yourself. These helpers are labels — they don't call any function, they only annotate this tape.
Option 1 — sibling log (simple). Call
webideTrace.tap('name', arg1, arg2) once per event.
Each tap shows up as a flat sibling. Use this when you just
want to know "did this code run?" or "in what order did these run?".
Option 2 — scope tracking (for nested / recursive calls).
Put webideTrace.call('name', args…) as the
first line inside the function body, and
webideTrace.return(value) immediately
before every return statement (or once at the end if the function is void).
Then call the function normally from outside.
// JavaScript example
function fact(n) {
webideTrace.call('fact', n); // at the top
if (n <= 1) {
return webideTrace.return(1); // wrap every return
}
let r = n * fact(n - 1);
return webideTrace.return(r);
}
fact(4); // now the tape shows fact(4) → fact(3) → fact(2) → fact(1)
Every call must be matched by a return.
If you put three calls in a row without
returns, each one ends up nested inside the previous (which
is what the IDE will warn about with "no .return"). For that case use
tap instead.