NoesisGUIPanel throwing inspector exception
Posted: 06 Feb 2017, 11:59
I'm currently experimenting with programatically setting the root XAML of the NoesisGUIPanel by setting the xaml path and then forcing a reload with ForceLoadXaml();
Works fine but if I have the NeosisGUIPanel open in the inspector while it happens, an exception is thrown:
Am I doing something wrong or is this a Unity or Noesis bug?
Edit: I just checked, even if I open the inspector for the panel anytime AFTER the fact, the exception also gets thrown. Apparently the field that shows the loaded XAML cannot be updated by the inspector if it is changed programatically? That seems to be a bug.
Works fine but if I have the NeosisGUIPanel open in the inspector while it happens, an exception is thrown:
Code: Select all
ArgumentException: GUILayout: Mismatched LayoutGroup.Repaint
UnityEngine.GUILayoutUtility.BeginLayoutGroup (UnityEngine.GUIStyle style, UnityEngine.GUILayoutOption[] options, System.Type layoutType) (at C:/buildslave/unity/build/Runtime/IMGUI/Managed/GUILayoutUtility.cs:268)
UnityEditor.EditorGUILayout.BeginVertical (UnityEngine.GUIContent content, UnityEngine.GUIStyle style, UnityEngine.GUILayoutOption[] options) (at C:/buildslave/unity/build/Editor/Mono/EditorGUI.cs:7217)
UnityEditor.EditorGUILayout.BeginVertical (UnityEngine.GUILayoutOption[] options) (at C:/buildslave/unity/build/Editor/Mono/EditorGUI.cs:7196)
NoesisGUIPanelEditor.OnInspectorGUI () (at Assets/Editor/NoesisGUI/NoesisGUIPanelEditor.cs:38)
UnityEditor.InspectorWindow.DrawEditor (UnityEditor.Editor editor, Int32 editorIndex, Boolean rebuildOptimizedGUIBlock, System.Boolean& showImportedObjectBarNext, UnityEngine.Rect& importedObjectBarRect) (at C:/buildslave/unity/build/Editor/Mono/Inspector/InspectorWindow.cs:1236)
UnityEditor.DockArea:OnGUI()Edit: I just checked, even if I open the inspector for the panel anytime AFTER the fact, the exception also gets thrown. Apparently the field that shows the loaded XAML cannot be updated by the inspector if it is changed programatically? That seems to be a bug.
