Copied from http://www.noesisengine.com/forums/viewtopic.php?f=3&t=1228

I noticed that the default exception handling in Noesis Unity in NoesisError.cs do not give back stack trace into my code in the Check() function.
If I change SetPendingError(...) to this, I get much better stack traces:
Code: Select all
private static void SetPendingError(string desc)
{
throw new NoesisException(desc); <---------- new code
// old and obsolete code below:
// Do not overwrite if there is already an exception pending
if (_pendingError.Length == 0)
{
_pendingError = desc;
}
}
Example:
Before: stack trace AFTER the error actually happened
[Exception] NoesisException: Target not found
View.Noesis_ViewTouchDown() Assets/NoesisGUI/Plugins/API/Core/NoesisView.cs:370
View.TouchDown() Assets/NoesisGUI/Plugins/API/Core/NoesisView.cs:218
NoesisView.TouchDown() Assets/NoesisGUI/Plugins/NoesisView.cs:258
NoesisExtensions.PointerDown() Assets/XAMLs/FantasiaPhone/NoesisExtensions.cs:179
ImagePointerEvents.ProcessPendingInputEventsIfAny() Assets/Scripts/ImagePointerEvents.cs:238
ImagePointerEvents.Update() Assets/Scripts/ImagePointerEvents.cs:127

After updat: stack trace AS the error happens:
[Exception] NoesisException: Target not found
Storyboard.Stop() Assets/NoesisGUI/Plugins/API/Proxies/Storyboard.cs:138
StoryboardExtensions.StopStoryboard() Assets/XAMLs/FantasiaPhone/UnityShared/StoryboardExtensions.cs:53
TiltEffect.StopTiltReturnStoryboardAndCleanup() Assets/XAMLs/FantasiaPhone/UnityShared/TiltEffect.cs:567
TiltEffect.BeginTiltEffect() Assets/XAMLs/FantasiaPhone/UnityShared/TiltEffect.cs:354
TiltEffect.TryStartTiltEffect() Assets/XAMLs/FantasiaPhone/UnityShared/TiltEffect.cs:284
TiltEffect.TiltEffect_ManipulationStarted() Assets/XAMLs/FantasiaPhone/UnityShared/TiltEffect.cs:194
UIElement.RaiseManipulationStarted() Assets/NoesisGUI/Plugins/API/Proxies/UIElement.cs:1729
Debug.LogException()
Error.SetNativePendingError() Assets/NoesisGUI/Plugins/API/Core/NoesisError.cs:40
UIElement.RaiseManipulationStarted() Assets/NoesisGUI/Plugins/API/Proxies/UIElement.cs:1734
View.Noesis_View_TouchDown()
View.Noesis_ViewTouchDown() Assets/NoesisGUI/Plugins/API/Core/NoesisView.cs:370
View.TouchDown() Assets/NoesisGUI/Plugins/API/Core/NoesisView.cs:218
NoesisView.TouchDown() Assets/NoesisGUI/Plugins/NoesisView.cs:258
NoesisExtensions.PointerDown() Assets/XAMLs/FantasiaPhone/NoesisExtensions.cs:179
ImagePointerEvents.ProcessPendingInputEventsIfAny() Assets/Scripts/ImagePointerEvents.cs:238
ImagePointerEvents.Update() Assets/Scripts/ImagePointerEvents.cs:127

Notice the extra TiltEffect.* stack traces that are very valuable - point to the actual code triggering the error.
Is it possible to improve/change the error handling in future update of Noesis to support the current error's stack trace like above? or is there a reason not to?

Regardless, I'll be using the new code with the "throw ..." that happens just in time, much more useful. :)