In the MVC+VS version of the Recordings application, one of the features that can be implemented with ease thanks to the architecture is the Time Travel Debugging.
I noticed that when traveling through the history of the View States, in case a view is presented on top of the actual View Hierarchy you lose access to the slide until you dismiss the actual view, which adds another view state to the history, in this case the culprit is the recording screen. Is that behaviour expected? If not, or even if it is, how would be a good way to not lose access to the slider when the history contains a screen that is presented on top of the actual view context?
In the MVC+VS version of the Recordings application, one of the features that can be implemented with ease thanks to the architecture is the Time Travel Debugging.
I noticed that when traveling through the history of the View States, in case a view is presented on top of the actual View Hierarchy you lose access to the slide until you dismiss the actual view, which adds another view state to the history, in this case the culprit is the recording screen. Is that behaviour expected? If not, or even if it is, how would be a good way to not lose access to the slider when the history contains a screen that is presented on top of the actual view context?