|
I sit behind a firewall , so I want my users to gather as much information as possible
|
|
|
|
|
Our applications reports a first look of the error and a reference to the log entry to check it if needed. We make a log file per day.
... she said you are the perfect stranger she said baby let's keep it like this... Dire Straits
|
|
|
|
|
What about: "No errors ever happen in my applications"? 
|
|
|
|
|
i'm sure some developers already spam their user with a messageBox under each button 
"ah ah, i know you clicked OK, didn't you ? "
|
|
|
|
|
Yes. I have contracted the habit, to write/develop perfect and error free software. Therefore I don't need any error message. 
\\\| \\ - -
( @ @ )
+---------------oOOo-(_)-oOOo-----------------+
| Stephan Pilz stephan.pilz@stephan-pilz.de |
| <a href=www.stephan-pilz.de>www.stephan-pilz.de</a> |
| ICQ#: 127823481 |
+-----------------------Oooo------------------+
oooO ( )
( ) ) /
\ ( (_/
\_)
|
|
|
|
|
I think that's equivalent to "I don't do error checking", which in turn is equivalent to "I let the OS or runtime handle error messages"
|
|
|
|
|
"An error occured that should not have happened ! Push the reset button to continue !"
|
|
|
|
|
Since I've seen what a hacker can do with a website that tells the user to much whats going on, I am a little less talkative to the user about what wend wrong in my application.
A basic description of the error with a little information on how to solve the problem is enough I think. Usually I will get a issuereport in the bugtracker or an e-mail message with that error, so that I can support my users from there.
WM.
What about weapons of mass-construction?
|
|
|
|
|
I agree, don't tell people more than they need to know.
I tell them that a report of their error was send to the administrators (this is true, the error and it's details is writen to a database or send by mail).
Unless the user experiencing this error is the administrator, then a detailed report is shown in the browser (and send anyway)
SvenL
|
|
|
|
|
Our error message boxes have two views. They pop up in user view, only a basic explanation of what went wrong is visible. A "Details"-Button opens the support view with original exception, stack trace, and so on. That means, the users don't get shocked by huge unreadable messages, but the support team still gets the full details.
____________________________________
There is no proof for this sentence.
|
|
|
|
|
ditto - its gotta have both.
|
|
|
|
|
I agree, but mostly i add a boolean in my error module so an admin can switch detailed error handling off and on. so the user is always informed but the admin can set detailed errors on in a control panel if he wants to solve the problem.
|
|
|
|
|
A lot depends on the application and its intended user base.
Some times detailed information is needed so it can be relayed to user-support.
Other times, it is better just to tell the user an error has occured and get them back to a state where they can continue to work.
Usually though, I stick with basic information displayed to the user and the detail written into the log files.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
