I was able to reproduce it... could you please report it in our bugtracker and we will fix it for the next version?
Thanks for your help!

It seems the .uasset corresponding to that .xaml file is out of sync. Thanks for reporting this, we will update it in the next version of the plugin.

For the time being, if you save it once, it shouldn't ask you anymore about unsaved assets in our theme.

The idea I proposed was to darken the ListBoxItem itself, not the whole ListBox. That way you decide, in a per-item basis, if you want to darken the item or not. I think it is a simpler approach to what you're trying to do. Could that work for you?

Hello, I've tried to reproduce your problem but it seems to be working as expected with latest version of Studio. This is the template that I tried and Studio generated: <ControlTemplate x:Key="ButtonTemplate" TargetType="Button"> <Border x:Name="BackgroundBorder" Backg...

I don't think that kind of OpacityMask can be created just using xaml because if it depends on the item that opens the ContextMenu. But, couldn't you just darken the background of all the items except for the one that opens the context menu with some trigger? Like "if I'm not showing the contex...

I think the problem is in the name used to register the event: public static readonly RoutedEvent InitialFocusEvent= EventManager.RegisterRoutedEvent( "InitialFocusEvent", RoutingStrategy.Direct, typeof(RoutedEventHandler), typeof(MyScreen)); Compared to when you hook to the event in the t...

Thanks!

The thing is that those delegates are created internally by the PInvoke code (by the C# marshaller), from a native funtion pointer. To get rid of that internal allocation, I can only think on changing our code so it doesn't require a native function pointer to be passed to the C# callback. But it is...

Thanks for taking the time to isolate this issue.

It looks like PInvoke marshalling automatically allocates those delegates when transitioning from C++ to C#. We'll try to find a way to avoid it but it doesn't look easy to do.

Hi,

This is a feature that our RiveControl does not support yet, could you please report it in our bugtracker and we will add support for it.
I think the best way is to just support in the InputName a path to the nested artboard like you tried to do.

Thanks!