Interesting idea. However thinking about this, it wouldn't be as simple to implement as it may seem first. We would need to recognize all error messages to distinguish the code or symbol names from the message parts to avoid coloring the words in the message as if would be a code. I mean you may use symbol name which are part of the error message string.
Another thing is there is an Error List Window
View -> Error List
which uses a listbox and I don't know if we can color this window.
It would definiately add value to the product but the question is that would it be enough to worth the effort?
quote:We would need to recognize all error messages to distinguish the code or symbol names from the message parts. ..I mean you may use symbol name which are part of the error message string.
The chances of a collision are definitely there, but remote, I think. Plus: It looks as if all symbols in an error message are enclosed in ''.
Example:
'xyz' is not a member of 'abcd'.
As for the error list I find it of limited use anyway. It is no more than a quick overview and it shows only the first line of an error message.
Either the error is so simple that I can spot it right away - even without coloring - or the error is more complicated, but then I have to switch to the output window to find out more about it.
Errors that stem from templates would benefit greatly from colors.
So a first step could be to simply parse the error messages for symbols enclosed in quotes '' and color these. That would probably go a long way already.
Coloring the output (build) window
Posted - Jul 15 2010 : 11:20:32 AM
