design of radio-button choice

[Richard Gaskin]

Sarah Reichelt wrote:
> I find it frustrating to come across a disabled button and not be  able 
> to see why it is disabled. In one application I am developing, I  have 
> adopted the following strategy for screens where a lot of data  must be 
> entered before proceeding: I put an invisible button  underneath the 
> disabled button. If the disabled button is clicked,  the click passes 
> through to the button underneath which can tell the  user what data is 
> missing. This saves people a lot of time trying to  work out why the 
> button is disabled, while giving them the visual  feedback that they 
> haven't finished. If the button is enabled, it  traps the click and the 
> information button underneath never gets used.

Tooltips could accomodate this as well, if only they worked when the 
control is disabled.

Another reason to vote for BZ#197:
<http://support.runrev.com/bugdatabase/show_bug.cgi?id=197>

--
  Richard Gaskin
  Managing Editor, revJournal
  _______________________________________________________
  Rev tips, tutorials and more: http://www.revJournal.com