Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
Sign upInt3 as component property causes GS to crash #383
Comments
This comment has been minimized.
This comment has been minimized.
The crash in Xaml UIElement probably means the template for the editor of If someone wants to investigate, the culprit could be in file https://github.com/xenko3d/xenko/blob/master/sources/presentation/Xenko.Core.Presentation/Themes/ExpressionDark/Theme.xaml#L4199 (at least that's a good starting point). |
This comment has been minimized.
This comment has been minimized.
Not sure if this is the problem but the |
This comment has been minimized.
This comment has been minimized.
To help investigate property grid issues, we have that test asset that can be used: https://github.com/xenko3d/xenko/blob/master/sources/editor/Xenko.Assets.Presentation/Test/TestAsset.cs Note that it currently doesn't include |
This comment has been minimized.
This comment has been minimized.
There is an extra Deleting it fixes it. |
[Presentation] Bugfix/int3 editor (xenko3d#387) (fixes xenko3d#383)
This comment has been minimized.
This comment has been minimized.
Do fixes to Game Studio also get pushed through nuget somehow or is this a more involved process? |
Release Type: Official Release
Version: 3.1.0.1-beta01-0441
Platform(s): Windows
Describe the bug
Adding a component property of the type Xenko.Core.Mathematics.Int3 causes Game Studio to crash with a confusing exception log upon attaching to any entity.
To Reproduce
Steps to reproduce the behavior:
Repro here: https://github.com/boriscallens/XenkoBuildRepro
[DataContract("MyComponent")]
public class MyComponent: EntityComponent
{
// public Vector3 Working { get; set; }
public Int3 Crashing { get; set; }
}
Expected behavior
The component is added to the entity and a Crashing property of the type int3 is editable on the component.
Alternatively/complementary a helpful error message and placeholder Unloadable component. Keeping GS functional for editing.
Alternatively a more helpful exception / stacktrace
Screenshots
N/A
Log and callstacks
buildLog.txt
Additional context
Maybe it has nothing to do with the type, but with the editor ui component?
That would explain the stacktrace pointing to XamlParseException: Add value to collection of type 'System.Windows.Controls.UIElementCollection' threw an exception.
From comparing the Int3 implementation with the Vector3 implementation I couldn't identify any relevant differences.