I have a form that can be populated with records from a grid. "reset" allows the...

y0ghur7_xxx · on April 13, 2011

Wouldn't that better be served by a "new" button?

xd · on April 13, 2011

From user acceptance testing we done, that gives the impression it would create a new record from the populated data.

Edit: we use the wording "Clear" not "Reset" btw.

f00li5h · on April 13, 2011

sounds like a "Please throw away everything I just typed" button to me ...

xd · on April 13, 2011

Your replies have prompted me to rethink the logic. I'm going to add some rules to the "Clear" button:

1, Hide the button whilst no records have been clicked. 2, If a record has been clicked, clicking the button clears the form then hides itself.

Feedback appreciated.

whouweling · on April 13, 2011

It may be better to not hide the button, but to disable it.

Hiding buttons in response to application state confuses the user.

(Imagine the user searching the screen for the "Clear" button which he or she knows should be there ...)

f00li5h · on April 13, 2011

an [x] button to get rid of the edit form - for don't save, or don't create (ideally with undo, but "are you sure" is good too)? maybe?