I would like to ask for your experience on this problem :
When an app gets an "too technical" error condition, will you display it as an error code or a descriptive string ?
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 ?
In general, I like using the ErrAlert API to show errors for which I cannot handle. That seems to be standard practice for network-based applications, due to the wide variety of errors that can come from that layer.
-- Ben Combee, senior DTS engineer, PalmSource, Inc. Read "Combee on Palm OS" at http://palmos.combee.net/
-- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
