View Issue Details

IDProjectCategoryView StatusLast Update
0004970NoesisGUIStudiopublic2026-04-09 09:49
Reporterdstewart Assigned Tosfernandez  
PrioritynormalSeveritymajor 
Status assignedResolutionopen 
Product VersionStudio_Beta 
Target VersionStudio_Beta 
Summary0004970: No Method To Determine Where a Property's Value Is Coming From
Description

Currently, in certain instances, it is possible for the Value Displayed in a Property's field to come from a different source than the Property Field directly.
For example, the value in the Property's Field could be overwritten by a Storyboard, a Setter, an Inheritance, etc...

Studio however offers no indication that a Property's Value comes from elsewhere, nor from where it originates.

This sometimes results in source mismatches between what is visible in the Properties Panel, on-Stage, and written to the XAML.

The resolution of this likely comes in 2 forms:

1) A visual indicator of some kind on the Property's in the Properties Panel, that a value is being influenced from elsewhere.

2) A tooltip displayed when hovering over the Property Value, the Property Name, and/or possibly the entire Property line hitbox, indicating where the value is coming from.


Repro Steps:

1) Create a Studio Project featuring a MainPage.xaml

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

3) Within the Template, navigate to the Interactivity/Setters Panel, and created 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.

Observe how the value continually 'snaps' back to '128', without any indication as to why it is refusing input.

Expected Results: An indicator is provided in an Element's Properties that show that a Property Value is under the influence from somewhere, and it is possible to find out where it is coming from.


PlatformAny

Activities

There are no notes attached to this issue.

Issue History

Date Modified Username Field Change
2026-04-08 12:00 dstewart New Issue
2026-04-09 09:49 sfernandez Assigned To => sfernandez
2026-04-09 09:49 sfernandez Status new => assigned
2026-04-09 09:49 sfernandez Target Version => Studio_Beta