Relates to: #126

from weevil.

Implementation Details

It turns out that this feature already existed in a slightly different form:

1. time gaps could be identified using the @Elapsed>3000 moniker
   • in this case 3000 represents a time period measured in milliseconds.
2. the built-in UI Responsiveness Analyzer was already comparing log entries generated by the UI thread (ThreadId=1) looking for periods of time where logging stopped

So a couple of small changes where made:

1. there is now a more generic implementation of the old UiResponsivenessAnalyzer called: TimeGapAnalyzer
2. Weevil's menu now has the following options:
   • Detect Time Gap
   • Detect Time Gap (UI Only)

It is worth noting that:

• the TimeGapAnalyzer will write the elapsed time into the record's comment
• whereas, the user still has the option to use the @Elapsed moniker if they do not wish to generate any comments

from weevil.