##ARexx
7 messages in this thread
Bill,
I've been trying for a while to get TRACE BACKGROUND to work – is there a
trick to it ? So far, when I've tried it, it appears to trace normally if
TS is used.
And is there any way of getting TCO to work with a WShell (DHOpts) style
window – I'd really like to kick off TCO, & have it sit there unnoticed
until/unless there was an error; I'd also like to use the scrolling in the
DHOpts style windows…
Cheers Graham
Graham, You'll need to do a
CALL trace('B')
to enter background tracing if intereactive tracing is already in effect.
This is because TRACE instructions (but not the function call) are ignored
if you're tracing interactively.
To change the TCO window, define a GLOBALCON clip list var and put the
desired console specification in it.
-Bill Hawes
Both those work perfectly – thanks very much – that's really going to make
my life a lot easier when I'm tracing.
One further thing I'm afraid – having tried GLOBALCON with an AUTO option,
I find that I can close the tracing console using the close gadget: however
the TCO command is still there, waiting. That's fine, but when something
happens that would cause trace output, the console re-opens, but nothing is
written to it. Obviously not really a problem, as I can TCC in the usual
way, but it would be nice if I could use the close gadget & have the
console return, with trace info, when needed again 🙂
Cheers Graham
Graham,
To have your global tracing console reopen after hitting the close gadget,
try including the /AUTO but not /CLOSE option in the console spec. The
AUTO option implies a close gadget, and the gadget functions as a temporary
or "soft" close, just like the CTRL-\ key. Putting a /CLOSE gadget gives
you a "hard" close, so that the console handler suppresses output and
issues control-C breaks back to any task that writes to the console.
-Bill
Bill,
Sorry, I didn't explain the symptoms clearly. I have been using just the
AUTO option: what happens is that if I then use the close gadget, it closes
the console OK. When I get another error or more trace info, the console
re-opens, displays previous messages, but doesn't display any new messages.
Any thoughts ?
Cheers Graham
Graham,
I'm have no problems here with the trace console reopening to display both
the old trace output as well as the new lines. Are you sure you don't have
a /CLOSE as part of the device-level default for the console you're using?
-Bill
Bill,
Ah – good point – yes I do. I've defined a new DH device now for my
ARexx debug console, and it's working fine.
Thanks very much – this is definitely going to help me a lot with the 'Oh
it went wrong – how can I reproduce it' syndrome – I won't need to, as the
evidence will be sitting there !
Cheers Graham