View Issue Details

IDProjectCategoryView StatusLast Update
0003524NoesisGUIStudiopublic2025-11-03 10:54
Reporterdstewart Assigned Tosfernandez  
PrioritynormalSeverityminor 
Status resolvedResolutionwon't fix 
Product VersionStudio_Alpha 
Target VersionStudio_BetaFixed in VersionStudio_Beta 
Summary0003524: Element-Level Storyboards Can't Be Created in Studio
Description

In XAML, it is possible to embed a Storyboard directly within an element, inline at the Element level, for example:

<Rectangle Name="MyRectangle">
<Rectangle.Triggers>
<EventTrigger RoutedEvent="Rectangle.MouseEnter">
<BeginStoryboard>
<Storyboard>
<DoubleAnimation Storyboard.TargetName="MyRectangle" From="100" To="200" Duration="0:0:1" />
</Storyboard>
</BeginStoryboard>
</EventTrigger>
</Rectangle.Triggers>
</Rectangle>

However, as far as I can tell, it is not possible to perform an equivalent operation within Studio successfully in a way that allows for usage, and editing in the same way that Page-level Storyboards support.
See Repro Steps for the two methods I attempted to achieve this.

Steps To Reproduce

Repro Steps:

METHOD 1: VIA THE ANIMATION PANEL

1) Create a Page

2) Navigate to the Animation Panel, then to its 'Storyboards' tab.
Observe how at the top of the Storyboards panel, it is written "Editing 'Page' Storyboards"

3) Select the RootGrid. (in order to mimick the behaviour that exists in Resources where you have to click a Navigator layer to get its scope active)
Observe how at the top of the Storyboards panel, it is not written "Editing '[Grid]' Storyboards".

Expected Results: Storyboards can be added to specific scopes in the same way that Resources can, by selecting them in the Navigator,
{This requires a wider feature/UX Discussion on how to best UX this, and how to potentially align the Resources and Storyboards Panels}


METHOD 2: VIA THE RESOURCES PANEL

1) Create a Page
2) Navigate to the Resources Panel
3) Select the Root Grid from the Navigator.
4) Select the Root Grid from the Resource Scope Browser.

5) Under the "Search a type of Resource to create" combobox, search for "Storyboard"
Observe how there is no Storyboard Resource option to add to the Root Grid element.

6) Navigate to the Animation Panel, then to its 'Storyboards' tab.
7) Create a new Storyboard, and add at least one keyframe that features a Property change (if not the Storyboard won't be detected in the next steps)

8) Return to the Resources Panel. In the Scope Browser, ensure that 'Page' is selected. You should see your newly-created Storyboard in the Resources List.
9) Select the Root Grid from the Navigator, this should make it appear in the upper Scope Browser section under the 'Page'.
10) Without deselecting the RootGrid in the Navigator, hover over the Storyboard resource.
11) Using the Grabber icon that appears on hover of the Storyboard, drag-and-drop the Storyboard into the Root Grid within the upper Scope Browser.
At this point, the Root Grid, and its included Storyboard Resource will disappear from view. (This is a separate bug related to auto-deselection of a layer when moving a Resource)

12) Select the Root Grid again from the Navigator. this should make it appear in the upper Scope Browser section under the 'Page'.
13) Select the Root Grid from the Resource Scope Browser. This should make the created Storyboard now be visible in the Resource Listing.

14) Navigate to the Animation Panel, then to its 'Storyboards' tab.

Observe how the Storyboard contained within the RootGrid's Resources is not visible, thus making the Storyboard animation impossible to edit or use.

Expected Results: Storyboards can be created from the Resources Panel.
Expected Results: Storyboards that are contained within an Element, can be edited via the Animation Panel.
Expected Results: Storyboards can be opened for edit directly from the Resources Panel, the same way that a Style or Template can (via the pencil button on hover)

PlatformAny

Activities

dstewart

dstewart

2025-10-30 15:39

developer   ~0011310

Demoting to Minor.

sfernandez

sfernandez

2025-11-03 10:54

manager   ~0011341

We decided to hide this workflow in Studio in favor of interactivity Triggers.

Unless we find any scenario that can't be solved with interactivity we can deprecate EventTriggers at element level.

Issue History

Date Modified Username Field Change
2024-07-18 12:33 dstewart New Issue
2025-04-02 11:08 sfernandez Target Version => Studio_Beta
2025-10-30 15:39 dstewart Severity major => minor
2025-10-30 15:39 dstewart Note Added: 0011310
2025-11-03 10:54 sfernandez Assigned To => sfernandez
2025-11-03 10:54 sfernandez Status new => resolved
2025-11-03 10:54 sfernandez Resolution open => won't fix
2025-11-03 10:54 sfernandez Fixed in Version => Studio_Beta
2025-11-03 10:54 sfernandez Note Added: 0011341