It would be "nice to have" a timer accessible from Execute scripts.
At a minimum, this timer should post time stamps in a convenient place like the console log. Perhaps it is only a matter of writing start / stop messages into the log and then later drilling into details would discover timestamps created by the log.
It would be nice to have the timer facility do the arithmetic to calculate elapsed time between timer start & timer stop. Perhaps it is possible to capture CPU time as well as elapsed time between timer start & timer stop. While it might be a bit over-the-top, perhaps downloadable files would allow convenient comparisons over multiple versions of the software.
While further investigation needs to be accomplished, the "[Violation] 'click' handler took 5473ms" messages available in the console log window may provide all the timing necessary.
It would be "nice to have" a timer accessible from Execute scripts.
At a minimum, this timer should post time stamps in a convenient place like the console log. Perhaps it is only a matter of writing start / stop messages into the log and then later drilling into details would discover timestamps created by the log.
It would be nice to have the timer facility do the arithmetic to calculate elapsed time between timer start & timer stop. Perhaps it is possible to capture CPU time as well as elapsed time between timer start & timer stop. While it might be a bit over-the-top, perhaps downloadable files would allow convenient comparisons over multiple versions of the software.