Page 1 of 1

[suggestion] Easier visualizer to identify what node in the Navigator has Trigger/VisualState etc

Posted: 07 Oct 2026, 15:55
by jinfox
Hello,
I was trying to identify the best way for me to not get lost when modifying an existing template or page to see, in a single look, where are the triggers, behavior and Visual state manager located.
361bf0c3-4d02-4996-8e86-111342a166ae.jpg
I have just made this quick mockup of that I thought it could look like but maybe there is a better way to do it?
What do you think about it?

Thank you!

Re: [suggestion] Easier visualizer to identify what node in the Navigator has Trigger/VisualState etc

Posted: 07 Oct 2026, 17:56
by fllorens
Hello,

This is a very timely topic, we are discussing a proposal to better show the user how a project is put together, starting with a configurable highlight/filter menu in the Navigator.

In our proposal we want to ensure that the hierachy of the page or template is always shown, and there's no need to expand every panel to look for highlighted elements.
I understand that your use case is going directly to elements that have Triggers / Behaviors, and showing what kind of interactive elements are present, isn't it?
Also I'm understanding that you want to see elements that have active Visual States? or maybe are affected by a Visual State keyframe?

If there's some other use case that you consider interesting, we'll love to add it to we already have. Right now we want to filter by Bindings, Styles, Templates, Data, and we're considering Animation ( Storyboards / Visual States ) and Interactive Elements.
For example a user would be able to select 'Bindings' and 'Triggers' and the coincident elements would have an indicator next to them.

Thanks for the proposal and your feedback, we appreciate it immensely.

Francesc

Re: [suggestion] Easier visualizer to identify what node in the Navigator has Trigger/VisualState etc

Posted: 07 Oct 2026, 18:39
by jinfox
I do not know exactly about Binding because this is kind of expected a bit everywhere so that would be a bit messy. My use case now is to avoid having to click on each container in the tree to see if it has trigger/behavior or not by clicking on . being able to see if any element is targeted by visual state change would be quite nice as well.

This becomes quite handy while we have a xaml text edition / noesis studio approach of creating elements (as a engineer I often end up doing text edition through Visual studio for quick edits but once I hand off to an artists for polish/advanced animation, the easier it is for artists to see where are those storyboards and triggers, the better it would be.