1. How should WEE handle multiple errors?
- Posted by dcuny Feb 02, 2015
- 1260 views
When I write code like this:
foo() bar() grill()
WEE reports back to me:
<0074:>::Errors resolving the following references:
I have to open up ex.err to see the details. Oh, noes! 
Pressing F4 is much simpler.
Now, the actual error is more complete:
<0074>:: Errors resolving the following references:
'foo' (junk.exw:1) has not been declared.
'bar' (junk.exw:2) has not been declared.
'grill' (junk.exw:3) has not been declared.
grill()
^
I would be much nicer if WEE presented the complete error, and F4 moved to the first unresolved error.
Also, being able to distinguish between an error in crash() and one reported by crash() would be awesome.
Thanks!
- David
2. Re: How should WEE handle multiple errors?
- Posted by PeteE Feb 02, 2015
- 1241 views
Yes, it would be nice. I'll add it to the todo item for rewriting the error dialog.
3. Re: How should WEE handle multiple errors?
- Posted by dcuny Feb 02, 2015
- 1250 views
Great! 
- David
4. Re: How should WEE handle multiple errors?
- Posted by PeteE Feb 04, 2015
- 1237 views
The view error dialog has been rewritten to show a listbox containing multiple lines of either the call stack or undeclared references. You can pick the line to go to, or open the ex.err file.
5. Re: How should WEE handle multiple errors?
- Posted by dcuny Feb 04, 2015
- 1235 views
Wow! Very slick!
- David
