View Issue Details

IDProjectCategoryView StatusLast Update
0004499NoesisGUIStudiopublic2026-05-07 17:06
Reporterdstewart Assigned Tosfernandez  
PrioritylowSeveritymajor 
Status assignedResolutionopen 
Product VersionStudio_Beta 
Target VersionStudio_Beta 
Summary0004499: Bindings Don't Update When Data Properties Are Renamed
Description

Currently, Studio features a fairly robust renaming system:

  • If a Resource is renamed, it gets renamed everywhere its employed.
  • If a Data Structure or Data Property get renamed, they get renamed in other Data Structures that employ them.

However, we have a gap in this system in that when a DataProperty is renamed, it does not get renamed in the Property-level Binding its employed in.

This results in, following a renaming of a DataProperty, to have to update every Binding bound to a DataProperty in every instance where its used.


Repro Steps:

1) Create a Studio Project featuring a MainPage.xaml, and place a TextBlock within it.

2) From the Data Panel, create a Data Structure, featuring a 'Number' Data Property.

3) From the Data Panel, create a Data Set for the Data Structure created in Step 2), and apply it to the Page.
If desired, the Number Value for the Property created in Step 2) can be input at this Stage too.

4) Select the TextBlock on the Stage, and in its 'Text' Property, select 'Create Binding', and from the Binding's 'Context' Tab , bind it to the DataProperty created in Step 2).
At this point, the number set in the DataSet should be reflected in the TextBlock.

5) Return to the DataPanel, select the DataStructure containing the Number Data Property, then double-click on its name and give it a new name.

Observe how the TextBlock on the Stage no longer displays the value that was displaying until this point.

6) Select the TextBlock once again, and expand the 'Text' Property to view where it is receiving its Binding from.
Observe that the Property is still displaying a stale, no longer-existing Data Binding.

Expected Results: When a DataProperty is renamed, its name is updated everywhere where it's employed.

PlatformAny

Activities

dfranjic

dfranjic

2026-04-29 00:50

developer   ~0012285

Not sure how possible this would be at least without being 'smart' about it and introducing new bugs. I left my thoughts in: https://www.noesisengine.com/bugs/view.php?id=4587 -- there can be {Binding Prop} in XAML code, but that Prop can reference a property from multiple different types (each having a 'Prop' property) or {Binding MyProperty.Color}, MyProperty can point to any kind of object, user's custom data object that happens to have 'Color' or it can point to even a SolidColorBrush.

dstewart

dstewart

2026-05-07 17:06

developer   ~0012309

Will not resolve for now, to be left open, and to be revisited in the future and if further issues arise.

Issue History

Date Modified Username Field Change
2025-11-10 14:46 dstewart New Issue
2025-11-11 14:18 sfernandez Assigned To => sfernandez
2025-11-11 14:18 sfernandez Priority normal => low
2025-11-11 14:18 sfernandez Status new => assigned
2025-11-11 14:18 sfernandez Target Version => Studio_Beta
2026-04-29 00:50 dfranjic Note Added: 0012285
2026-05-07 17:06 dstewart Note Added: 0012309