View Issue Details

IDProjectCategoryView StatusLast Update
0004843NoesisGUIStudiopublic2026-03-28 02:36
Reporterdstewart Assigned Todfranjic  
PrioritynormalSeveritymajor 
Status resolvedResolutionfixed 
Product VersionStudio_Beta 
Summary0004843: Inside of a Template, Gradient Stop Colour Changes Aren't Part of Undo/Redo Stack
Description

Currently, if changes to Linear Gradient Stops are made within a Template, they cannot be undone and redone via the Undo/Redo Stack.

This appears to happen exclusively within a Template, and does not impact Gradient Stops created on an Element directly within a Page.

See attached video.


Repro Steps:

1) Create a Studio Project Featuring a MainPage.xaml

2) Introduce a ProgressBar Element to the root Grid of the Page, give it a 'Value' value to be able to see its fill.

3) Create a Template for it the ProgressBar, named and saved as desired.
This will open the Template in the Template Dummy Editor.

4) Select the PART_Indicator Border Element in the Navigator, and change its 'Background' Property to a Linear Gradient.

5) Change the colour of each of the two Gradient Stops to any two new colours.

6) Close the Brush Picker panel, and multiple times, press Ctrl+Z or undo via the HambugerMenu's 'Edit' section.

Observe how each of the individual colour stop changes within the Linear Gradient are not sequentially undone.

7) Once a multiple of 'undo' actions have been performed, perform the opposite action and 'redo' a multitude of changes.

Observe how the colour changes made in Step 5) are unrecoverable.

Expected Results: Gradient Stop changes are included as part of the undo/redo stack.

Attached Files
PlatformAny

Activities

dfranjic

dfranjic

2026-02-26 17:38

developer   ~0011960

Note for future: This happens probably due to the unsealed value getting stuck / not cleared properly. There is also danger of this happening in TransformProperty, as it directly modifies the objects RenderTransformOrigin and there's probaly a scenario where it isn't cleared before a command, making it not undo on Ctrl+Z.

dfranjic

dfranjic

2026-03-28 02:36

developer   ~0012129

The actual cause was that the object was sealed and thus undo was unsuccessful at modifying to the original values. Fixed in r16921.

Issue History

Date Modified Username Field Change
2026-02-26 17:21 dstewart New Issue
2026-02-26 17:21 dstewart File Added: 2026-02-26 11-09-29.mp4
2026-02-26 17:30 dfranjic Assigned To => dfranjic
2026-02-26 17:30 dfranjic Status new => assigned
2026-02-26 17:38 dfranjic Note Added: 0011960
2026-03-28 02:36 dfranjic Status assigned => resolved
2026-03-28 02:36 dfranjic Resolution open => fixed
2026-03-28 02:36 dfranjic Note Added: 0012129