Currently, if a Property's Value is under the influence from a different source (eg Setter, Animation, etc...), changing the Value of the Property directly in Studio fails to mark the Property as having an active Local Value.

This is typically done with the help of a blue outline on the Property's field, and a blue colouring of the Property's name

See attached video.

Repro Steps:

1) Create a Studio Project featuring a MainPage.xaml

2) Introduce a Button to the Page, and create a Template for it, saved to GlobalResources.xaml.
This will open the Button in the inline Dummy Template Editor.

3) Within the Template, navigate to the Interactivity/Setters Panel, and create a new 'When Property Changes' Setter.

4) Set this new Setter to be SourceName: 'Self', Property: 'IsEnabled', and Value: 'True'

5) Within this Setter, change the Corner Radius Property of the 'BackgroundBorder' Border Element to 128.
This will make the Button have four 128px radius corners immediately.

6) Within the Interactivity/Setters Panel, select 'No Setters Applied' at the top of the Panel, then select the 'BackgroundBorder' Element in the Navigator.

7) Attempt to change the 'BackgroundBorder' Corner Radius value to a specific different value of your choice..
Disregard how the value cotinually 'snaps' back to '128'.

8) Save all open documents,

9) Open GlobalResources.xaml in your preferred code editor.

Observe how though in Studio, the Property reads out '128', in the XAML code, the Corner Radius value corresponds to the value input during Step 7).
Observe that therefore, a local value has been applied to this Element.
Observe how in Studio, the Corner Radius is missing its blue colour-coding that usually demonstrates that it contains a Local Value.

Expected Results: A Property that contains a local change in XAML, has this reflected in the Studio Properties Panel via a blue colour-coding.