Fix/update apply app data method

[markgalvan-intel]

Updating app provider attachment methodology. Instead of finding and attaching to the closest Present Start, will now attach to the Present where the app provided present start resides in the Present Start and Present End interval. Note this only used in the absence of the app frame it.

[Copilot]

Pull request overview

This pull request updates how app/provider timing data is attached to PresentEvents, changing the matching logic from “closest earlier PresentStart” to matching based on whether the app-provided present start timestamp falls within the Present_Start → Present_Stop interval (with PC-latency keeping the prior heuristic behavior).

Changes:

• Extend ExtractAppTimingData() to accept a present stop timestamp and a mode flag to select matching strategy.
• Update call sites to pass Present_Stop time when attaching app timing data, and compute a stop bound for PC-latency attachment.
• Implement interval-based selection for non-PC-latency timing data (time-in-window match).

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
PresentData/PresentMonTraceConsumer.hpp	Updates ExtractAppTimingData() signature to include presentStopTime and a mode flag.
PresentData/PresentMonTraceConsumer.cpp	Passes present stop time into app-timing attachment and implements window-based timing-data selection logic.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[planetchili]

Looks good to me, great stuff!