drjdpowell Posted October 31, 2022 Report Share Posted October 31, 2022 This is a question to ask how people display errors to non-programmer Users. An example of a current Error Mesage that might be displayed to a User of one of my programs is this: The problem I find is that to a many, if not most, Users, this comes across as "Error N ocurred at blah, blah, blah, I'd better report this to the programmer". Their eyes have glazed over at the VI name, long before getting to the useful info that might actually help them fix the problem themselves (like realizing that they haven't pointed to the right folder where the file exists). I tend to get reports like "Error X happened", or even "It didn't work" . This is particularly bad with Error 1172, a .NET exception, which is full of .NET mumbojumbo like "invocation" and "inner exception". I would rather have error dialogs like this: Here, the info useful to the User is directly on the first line, followed by clear description not cluttered by techy-sounding fluff. Details only important to me, the Programmer, are at the back, where I don't care if the User has stopped reading. However, I am not sure how to programatically reorder Error dialogs in this way. The important key phrases such as "File Not Found" are buried in unstructered text. What have other people done? Quote Link to comment
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.