View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0003438NoesisGUIStudiopublic2024-06-27 14:052025-07-15 20:49
Reporterdstewart Assigned Todfranjic  
PrioritynormalSeveritymajor 
Status assignedResolutionopen 
Product VersionStudio_Alpha 
Target VersionStudio_Beta 
Summary0003438: Animation Property Values Unexpectedly Change When Unrelated Properties are Changed.
Description

There seems to be an issue where when a TranslateX is performed on a Storyboard, the Opacity Property Value of an Element is changed alongside it, even if the on-stage representation of the element is correctly reflecting the user-input value for it.

Steps To Reproduce

Repro Steps:

1) Open the Z3L_LiveDemo Sample Project
2) Select the fully-styled Main Menu button on the MainPage (Story Mode), right-click, and enter it to edit its Template.
3) Navigate to the Animation Panel, and select the MouseOver Visual State. This will cause the Animation Timeline to appear.
4) In the Navigator, select the layer named "MenuButton_Subtitle_TextVariants"
5) At the 0s mark, set the Opacity of this layer to 0%, and set its RenderTransform 'TranslateX' value to -32.
6) Without deselecting the "MenuButton_Subtitle_TextVariants" layer, move the Playhead to 1s.

Observe how the Opacity Value for the layer is correctly set to 0%.

7) Set the RenderTransform "TranslateX" value to 0.

Observe how the unrelated Opacity Value for the layer changes to 100%. Observe however how the layer on the Stage is correctly displaying as a 0% opacity layer.

Expected Results: Unrelated Properties within a storyboard do not change their values unless manually changed by the user.
Expected Results: The on-stage representation of elements reflects the value displayed in the associated Property

PlatformAny

Activities

dfranjic

dfranjic

2025-07-15 20:49

developer   ~0010912

Leaving a note for future (self/developer): This is due to a custom transform (hand written XAML). When user tries to animate in the Studio, it automatically generates a <TransformGroup> for the local value, rendering the existing animation invalid/incorrect, causing problems for Studio.

Issue History

Date Modified Username Field Change
2024-06-27 14:05 dstewart New Issue
2024-06-27 14:15 jsantos Assigned To => dfranjic
2024-06-27 14:15 jsantos Status new => assigned
2024-06-27 14:15 jsantos Target Version => Studio_Alpha
2025-04-02 11:09 sfernandez Target Version Studio_Alpha => Studio_Beta
2025-07-15 20:49 dfranjic Note Added: 0010912