realbasic-nug
[Top] [All Lists]

Showing errors to the user

To: REALbasic NUG <realbasic-nug@lists.realsoftware.com>
Subject: Showing errors to the user
From: Arnaud Nicolet <anic297@mac.com>
Date: Sun, 26 Jul 2009 17:18:28 +0200
Authentication-results: mx.google.com; spf=neutral (google.com: 74.124.194.228 is neither permitted nor denied by best guess record for domain of realbasic-nug-bounces@lists.realsoftware.com) smtp.mail=realbasic-nug-bounces@lists.realsoftware.com
Delivered-to: listarchive@realsoftware.com
Reply-to: REALbasic NUG <realbasic-nug@lists.realsoftware.com>
Sender: realbasic-nug-bounces@lists.realsoftware.com
Hello,

I'm wondering what is the best way for showing to the user that an error occurred (like the LastErrorCode of the folderitem class). On most Apple applications, like the Finder, QuickTime or i<something>, it seems they try to show human-readable explanations as often as possible (instead of -43, they show "The file could not be found", etc.). But how have them included all the error codes in their source code (I mean, where can I look up for these error codes, as the most complete list)?

On the other hand, many applications just show the error code. This seems wrong to me because the user has to know why something failed. It just avoids searching for the meaning of these error codes each time one makes an application.

I'm wondering if someone has already solved this question...

_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>

Search the archives:
<http://support.realsoftware.com/listarchives/lists.html>


<Prev in Thread] Current Thread [Next in Thread>