Thanks for the ticket, we've found the source of the problem and fixed it for the next release.

You are right, that ticket is already resolved and Noesis.GUI.Extensions nuget supports .NET and .NETCore as well as .NET Framework projects since 3.0.9 version. Thanks for pointing this out.

Thanks for sharing the solution, even if it wasn't a Noesis issue :)

Hi, this looks like something is wrong in our code because if the source of the behavior is always the same it should reuse the offscreen texture for all instances. Could you please report this in our bugtracker?

Just for reference for other users, in the ItemTemplate you shouldn't put a TabItem, as I explained above the TabItem is automatically created by the TabControl when using ItemsSource. So either you use a TextBlock in the TabItem template and bind its text directly to the appropriate item property (...

Hi, For a TabControl that uses ItemsSource, TabItems are automatically created by the TabControl for each item in the source collection, and it assigns the style set in ItemContainerStyle property, so this is where you have set your custom TabItem style: <TabControl x:Name="BuildingTabs" I...

Thanks a lot for the repro, I was able to find what was going on and provided some patches in the tracker.

Hi, sorry for the very late reply but we were trying to get our heads around this problem. One way to be implemented from outside is by specify some attached property to define if a control is being controlled by any specific gamepad (so you can use this to show some visual cue in your templates), a...

The Setter.Property uses a converter to find the dependency property from the name. In case the Setter is used inside a Style or a Template, if you don't specify a TargetName, it can use the TargetType to resolve the type to search for the property. As you're not inside a Style or Template you need ...

You can have a collection of collections if you need some kind of grouping, if that makes sense.
For example a list of categories, and then each category a list of options.
In that scenario you can even define expanders for each category to group each list of options.