Currently, in a Studio Project containing multiple Documents (XAML Pages), if one Document is open, and the user presses 'Play', then switches to the tab of a second document (without pressing 'Stop'), they moment they attempt to Generate Sample Data for the second Document, the operation succeeds in the Data Set, but fails to update on-Stage.

See attached video.

Repro Steps:

1) Open the MiniShowcases Studio Project.

2) From the Assets Panel, Open the '9Slicing.xaml' Document in the Project root.

3) With 9Slicing.xaml open in a tab, press 'Play' at the top of the screen.
This will put the Document into 'Play Mode'

4) IMPORTANT: Without pressing 'Stop' or pressing [Ctrl+P], or closing 9Slicing.xaml from the Resources Panel,select DataGeneration.xaml to open it in a new tab.

5) Navigate to the Data Panel, identify, and expand the Data Structure named 'DataGeneration_Map_Collection', then click on the Data Set named 'DataGeneration_Map_Set'.
This will open the Data Set for this Document in the Properties Panel.

6) Within the 'DataGeneration_Map_Set' Properties, expand any/all of the Data Properties to reveal their values.

7) Either from the Data Set's Properties Panel, or from the Data Panel on the right of the screen, press the 'Generate Sample Data' button to generate new procedural values for this Data Set.

Observe how the values in the Data Set change successfully, but what is displayed on-Stage is not impacted by the changes in the Data values.

8) Close and re-open Studio, re-open 'DataGeneration.xaml', and repeat Steps 5) to 7).

Observe how now the Data Generation correctly updates what is displayed on the Stage.

Expected Results: Changing tab on an open Document stops 'Play Mode' for it, and automatically puts it into 'Stop' mode, thus not taking captive the rendering required to Generate Sample Data in a newly-opened Document tab.