This issue is related to:

Frame Window Shrinking: Reduce the frameCount setting in Profiler preferences while a frame with a screenshot is selected. Verify the screenshot is hidden if its frame falls outside the new window, validating the new check in ScreenshotIndexCatalogue.TryResolveDisplayedScreenshot.

e068e681-88cd-413f-8dbb-48567e67572a.mov

What I find a bit wrong is that it looks to retain the frame you had selected even though that has now been pushed out of the selection range. The screenshot module then looks to highlight the first frame it has access to, this results in the whole thing looking quite out of sync. Agnese Caglio (@agnese-caglio) do you have any thoughts here?

Steps to reproduce:

Load a large capture that has 4,000 frames in it
Select a screenshot near the start of this (Frame 5 for example)
Go into the Profiler preferences and reduce the 'Frame Count' to 600 frames
Go back to the Profiler and notice it still has the frame selected (however this is now out of the range of selectable frames)

Actual results: Frame is still selected even though it's out of range

Expected results: Frame in no longer selected (maybe the lowest available one is or no frame selected?)

Reproducible with versions: 6000.7.0a6

Not reproducible with versions:

Can’t test with versions:

Tested on (OS): Mac

Notes: