Maybe a dialog is not the way to go in those circumstances. If it's a choice between several things that are not standard yes/no choices, perhaps a menu or radio button would work better? I have always seen dialogs as a way to interrupt the normal flow of data entry, and alert the user to a condition that needs closer attention.
I suppose in the case of things like print dialogs that doesn't hold true, but then the print dialog is not really being used as a classic dialog, but rather a mini data entry form in it's own right. Bob On Sep 5, 2012, at 8:08 AM, Dr. Hawkins wrote: > On Tuesday, September 4, 2012, Bob Sneidar wrote: > >> Personally I like prompting the user click the button, using hotkeys as a >> less than obvious means. > > > I generally view amply circumstance in which the user is forced to use the > mouse in the middle of a routine data entry task as a catastrophic > interface design flaw, at a level that would stop me from buying the > program. > > > > -- > The Hawkins Law Firm > Richard E. Hawkins, Esq. > (702) 508-8462 > hawkinslawf...@gmail.com > 3025 S. Maryland Parkway > Suite A > Las Vegas, NV 89109 > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
