Improve Debug Report timeline readability, navigation, filtering, and event statistics

[vibhor1102]

The Debug Report is already very useful for understanding what happened during a Scenario execution, but I think a few improvements could make it significantly easier to read and navigate, especially for longer-running or more complex Scenarios.

I would like to suggest the following changes.

1. Replace hh:mm:ss.ms timestamps in the Timeline with readable relative elapsed times

The current Timeline shows cumulative timestamps such as:

00:00:00.226
00:00:00.526
00:00:01.645

Although precise, this format is difficult to scan quickly and makes it harder to understand how much time actually passed between events.

A more readable approach would be to show the time elapsed since the previous Timeline event:

226 ms
+300 ms
+1.04 s
+12.6 s
+2m 14s

For the first Timeline entry, the value could be shown without the +, since it represents the time from Scenario start.

This would make the Timeline easier to understand at a glance because the user can immediately see the delay between consecutive events rather than mentally calculating the difference between cumulative timestamps.

Preserve full timing precision in the event detail header

The detailed event screen does not have an obvious place for a separate timing statistics card, so I think the timing metadata could instead be incorporated directly below the event title.

For example:

Not Found Match
Frame #52 · 2.755s elapsed · +1.110s

This keeps the information visible without adding another card or interfering with the existing Conditions, States, and Counters tabs.

For users who need the raw values, tapping the metadata line could expand it or open a small details popup showing:

• Elapsed from Scenario start: 00:00:02.755
• Since previous event: 00:00:01.110
• Frame: #52

This would keep the main Timeline readable while still preserving complete debugging precision where it is needed.

---

2. Make the Timeline scrollbar draggable

When the Timeline contains many entries, a scrollbar appears on the right side.

Currently, it appears to act only as a visual position indicator.

It would be much more useful if the scrollbar thumb could also be dragged directly, allowing the user to move quickly through a long Timeline.

This would be especially helpful for long-running Scenarios where manually scrolling through hundreds or thousands of Timeline entries can take significant time.

Expected behaviour:

• Drag the scrollbar thumb upward or downward.
• The Timeline position updates continuously while dragging.
• The scrollbar continues to behave normally as a visual position indicator when not being dragged.

---

3. Fix terminology in Timeline Filters

In the Timeline Filters screen, the label currently reads:

Image Conditions

I believe this should instead be:

Screen Conditions

This would match the terminology used elsewhere in the app and better describe the type of conditions being filtered.

---

4. Add per-event occurrence statistics to the Overview

It would be useful to see how many times each event occurred during the Scenario execution.

The current Overview already shows aggregate information such as:

• Total duration
• Frames processed
• Average processing duration
• Screen Events fulfilled
• Trigger Events fulfilled

However, it does not show the occurrence count of each individual event.

I suggest adding an Event activity section at the bottom of the Overview.

A compact preview could show something like:

Event activity
12 unique events · 286 total occurrences
Most frequent: Not Found Match — 247×
>

Tapping the section could open a detailed event-count list.

Example:

Screen Events

Builder Attack — 6
Find — 18
Not Found Match — 247

Trigger Events

Start Scenario — 1
Attack Counter Reached — 3

This information belongs naturally under Overview because it is aggregate execution data, whereas Timeline is primarily chronological.

I would prefer this approach over adding a third bottom navigation tab, since keeping only Overview and Timeline makes the Debug Report interface simpler.

Sorting

The event-count screen could have a sorting button at the bottom-right, similar to the filter button currently used in the Timeline.

The sorting menu could provide:

• Default Sequence
  Uses the Scenario sequence defined by the user while creating the Scenario.

• Most Frequent
  Sorts events by occurrence count, highest first.

• Execution Order
  Sorts according to the order in which events first occurred during the actual Scenario execution.

I think Default Sequence should remain the default because it directly corresponds to the Scenario structure created by the user, while the other two modes would be useful for debugging and analysis.

---

5. Simplify the time format in Timeline Filters

The Timeline Filters screen currently also uses the full hh:mm:ss.ms format for the selected time range.

For example:

00:00:00.000 to 00:00:09.308

I think this is unnecessarily precise for manually adjusting a filter range.

A more readable adaptive format would be preferable.

Examples:

For a Scenario lasting seconds:

0s to 9.3s

For a Scenario lasting minutes:

0m 0s to 43m 21s

For a longer Scenario:

0h 00m to 2h 17m

The general idea would be to display only the two most relevant time units.

Possible adaptive formatting rules:

• Under 1 minute: seconds, optionally with one decimal place
  Example: 0s to 43.2s

• Under 1 hour: minutes and seconds
  Example: 0m 0s to 43m 21s

• 1 hour or longer: hours and minutes
  Example: 0h 00m to 2h 17m

This should provide more than enough precision for manually selecting a Timeline range while making the values considerably easier to read.

The underlying filter can, of course, continue operating with millisecond precision internally.

---

Summary

The overall suggestion is to make the Debug Report easier to scan and navigate without removing any detailed debugging information.

The requested improvements are:

1. Use readable relative elapsed times in Timeline entries instead of full hh:mm:ss.ms timestamps.
2. Show compact timing metadata directly below the event title in the event detail screen, with full raw timing available on tap.
3. Make the Timeline scrollbar draggable.
4. Rename Image Conditions to Screen Conditions.
5. Add an Event activity section to Overview with per-event occurrence counts and sorting options.
6. Replace full-precision timestamps in Timeline Filters with a simpler adaptive two-unit time format.

I believe these changes would make the Debug Report considerably easier to use for both quick inspection and deeper debugging, especially for long or complex Scenario executions.

[vibhor1102]

Thanks @hatbrox for the initial idea of the 4th suggestion.

[vibhor1102]

In addition to 2nd suggestion, the scroll bar should also have a greater minimum height so as to be more easily visible and draggable.

Thanks @willross42 for the suggestion.

[vibhor1102]

Restored back after a month of invisibility as my account was false-positively flagged