Vu Pham wrote:
For example, to connect to a server, it may have different kinds of errors :
no server found, protocol not supported, invalid cert, cert expiration,
timeout, connection made but no reply after that .....
In this case, which one will cause less annoying to the *users* : an error
code, or an explanation ?
I would think that the error code is usually meaningless to a user,
unless they are prepared with fore-knowledge or they have been
instructed on where to look for the meaning of the code. Without the
description, a user would experience the error, be presented an error
code, and likely wouldn't know what to do to resolve the issue. The
description would certainly be better in a lot of cases. However, there
might be too many indivicual error codes for you to want to present all
descriptions. You could group them together and present the error code
and the 'group' text description. So the user knows basically what's
wrong, and could then look up the specific code if they needed to. My 3
cents. Bob.
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/support/forums/
