On Fri, Aug 16, 2002 at 04:29:12PM -0400, Chris Beggy wrote: > On 16 Aug 2002, "Steven D'Aprano" <[EMAIL PROTECTED]> wrote: > > > On Thu, Aug 15, 2002 at 03:44:11PM +0100, Richard Lyons wrote: > > > I don't know about everyone else, but about half the time I spend on > > > bookkeeping is taken up chasing things I posted wrongly. My most common > > > error is caused by haste - leaving a drop-down box with its default contents. > > > > If the UI allows common errors like this, then its a UI bug. > > I don't think I agree that this is a UI bug.
What else would you call it? It is part of the UI that doesn't work the way it is intended to, and it causes errors. The point of having default data pre-entered into a field or drop-down is to make less work for the user. If it makes more work, then it is a bug. Not a coding bug, but still a bug. > What behavior would you propose? How would you implement it, or > what's an example of a good implementation? I'd say the easiest way to fix it would be to simply remove the default contents from the drop-down, and not let the user save the record unless they enter something into it. If you wanted to be more sophisticated, you could remember what they used last, and give that as the default. Note that "more sophisticated" is not necessarily better. Or you could let the user define a default setting. -- Steven D'Aprano Operations Manager Cybersource Pty Ltd, ACN 053 904 082 Level 9, 140 Queen St, Melbourne VIC 3000 Tel: +61 3 9642 5997 Fax: +61 3 96425998 Web: http://www.cyber.com.au ------------------------------------------------------- This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE! https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 ------------------------------------------------------- (un)subscribe: http://lists.sourceforge.net/lists/listinfo/sql-ledger-users Archive: http://www.mail-archive.com/[email protected]/
