Page 1 of 1
Updated to latest, can't find xaml files anymore?
Posted: 29 Oct 2013, 01:21
by kaban
After updating to the latest build Noesis seems to no longer be able to find xaml files, here is an error I get when attempting to run the button sample:
Exception: Assets/NoesisGUI/Samples/ControlGallery/Samples/Button.xaml resource not found
Noesis.Error.Check () (at Assets/Plugins/NoesisGUI/Scripts/Core/NoesisError.cs:49)
NoesisGUISystem.Noesis_LoadXAML (System.IntPtr& root, System.String xamlFile) (at Assets/Plugins/NoesisGUI/Scripts/Core/NoesisGUISystem.cs:370)
NoesisGUISystem.Load[FrameworkElement] (System.String xamlFile) (at Assets/Plugins/NoesisGUI/Scripts/Core/NoesisGUISystem.cs:80)
NoesisGUISystem.LoadXaml[FrameworkElement] (System.String xamlFile) (at Assets/Plugins/NoesisGUI/Scripts/Core/NoesisGUISystem.cs:34)
NoesisGUIPanel.Awake () (at Assets/Plugins/NoesisGUI/Scripts/NoesisGUIPanel.cs:68)
This is just with an update and nothing else...
Re: Updated to latest, can't find xaml files anymore?
Posted: 29 Oct 2013, 02:01
by ai_enabled
kaban, have you tried to click Build in the NoesisGUI Settings Panel? Usually this exception message means "something not built".
Re: Updated to latest, can't find xaml files anymore?
Posted: 29 Oct 2013, 02:49
by kaban
I just tried it, all it does is cause the unity editor to stop working and crashing out...
{{{
Unhandled exception at 0x7706E793: Access Violation reading location 0x00001167
}}}
{{{
[ 0] [0x7706E793] ntdll.dll
[ 1] [0x1FE97712] Noesis.dll
[ 2] [0x1FE9A1F6] Noesis.dll
[ 3] [0x1F864CD6] Noesis.dll
[ 4] [0x1FA1B318] Noesis.dll
[ 5] [0x1FC76170] Noesis.dll
[ 6] [0x1FC79B43] Noesis.dll
[ 7] [0x1FC7713B] Noesis.dll
[ 8] [0x1F8B32B9] Noesis.dll
[ 9] [0x1F8B46FB] Noesis.dll
[10] [0x1F8B6AAE] Noesis.dll
[11] [0x1FC7F97F] Noesis.dll
[12] [0x0BAF6EAF]
[13] [0x08EA84D9] mono.dll
[14] [0x08E6D9B2] mono.dll
[15] [0x08F2FCF6] mono.dll
[16] [0x08EA3B7A] mono.dll
[17] [0x08E9D603] mono.dll
[18] [0x08EA2451] mono.dll
[19] [0x08E6F404] mono.dll
[20] [0x1698A488]
[21] [0x16989330]
[22] [0x16A1FF95]
[23] [0x1295956D]
[24] [0x129594D7]
[25] [0x1297CAD1]
[26] [0x08E41E2E] mono.dll
[27] [0x08F2FCF6] mono.dll
[28] [0x08E9D603] mono.dll
[29] [0x00835828] Unity.exe
[30] [0x0083541A] Unity.exe
[31] [0x00822897] Unity.exe
[32] [0x00E8CD61] Unity.exe
[33] [0x00E8DBF8] Unity.exe
[34] [0x00E8F07E] Unity.exe
[35] [0x76A2775E] USER32.dll
[36] [0x76A28C2A] USER32.dll
[37] [0x76A284E5] USER32.dll
[38] [0x76A288F1] USER32.dll
[39] [0x00EA2D50] Unity.exe
[40] [0x00EA3C6C] Unity.exe
[41] [0x00FB1E7F] Unity.exe
[42] [0x767A495D] KERNEL32.DLL
[43] [0x770798EE] ntdll.dll
[44] [0x770798C4] ntdll.dll
}}}
Re: Updated to latest, can't find xaml files anymore?
Posted: 29 Oct 2013, 03:07
by ai_enabled
kaban, our team have problem on build too. The NoesisGUI team respond me yesterday they're started to investigate this issue. We keep using the 1.1.0 version at now.
Re: Updated to latest, can't find xaml files anymore?
Posted: 29 Oct 2013, 11:56
by sfernandez
Hi,
We are working hard to solve these problems right now. We finally are able to reproduce the crashes (thanks to the xaml sources provided by ai_enabled), and are trying to find what is happening.
Sorry for the inconveniences. We will keep you informed.
Re: Updated to latest, can't find xaml files anymore?
Posted: 02 Nov 2013, 00:39
by sfernandez
We found one of the reasons of the stability problems when building xaml files in Unity. It is important that user created classes that define dependency properties don't use the readonly keyword. A dependency property definition must look like this:
using System;
using Noesis;
[Noesis.Extended]
[Noesis.UserControlSource("Assets/UserControls/ColorPicker.xaml")]
public class ColorPicker : UserControl
{
public static DependencyProperty ColorProperty = DependencyProperty.Register(
"Color",
typeof(SolidColorBrush),
typeof(ColorPicker),
new PropertyMetadata(null));
public SolidColorBrush Color
{
get { return GetValue<SolidColorBrush>(ColorProperty); }
set { SetValue<SolidColorBrush>(ColorProperty, value); }
}
}
In the next version we will add some checks to detect definitions using the readonly keyword to avoid undesired crashes.