|
|
Maybe a #timer feature. The syntax would be:
#timer TIMER_ID, "timer text" start|stop|pause
TIMER_ID would allow multiple timers. It would be used like this:
#timer 1, "start of tree timer, first tree" start
DoTree()
#timer 1, "finished with first tree" pause
DoOtherStuff()
#timer 1, "starting second tree" start
DoTree()
#timer 1, "finished with second tree" stop
The output would be like this:
START TIMER: 1|start of tree timer, first tree
parse time:xx hours, xx minutes, and xx seconds
timer time:xx hours, xx minutes, and xx seconds
PAUSE TIMER: 1|finished with first tree
parse time:xx hours, xx minutes, and xx seconds
timer time:xx hours, xx minutes, and xx seconds
START TIMER: 1|starting second tree
parse time:xx hours, xx minutes, and xx seconds
timer time:xx hours, xx minutes, and xx seconds
STOP TIMER: 1| finished with second tree
parse time:xx hours, xx minutes, and xx seconds
timer time:xx hours, xx minutes, and xx seconds
"parse time" would be the total duration of parsing up to that point,
"timer time" would be the amount of time accumulated in that timer up to
that point.
In the timer statement, "start" would start the time accumulating in the
timer, "pause" would stop the time accumulation, and "stop" would do the
same as "pause" but would also reset the timer accumulator to 0. They
would output the text to the status window formatted something like the
above, similar to #debug, #render, etc.
--
Chris Huff
e-mail: chr### [at] yahoocom
Web page: http://chrishuff.dhs.org/
Post a reply to this message
|
|