Sorry that I've taken a while to respond to this but the first useful component I
wrote was a listbutton
which has an itemindex and a list of captions for this purpose (source free if you
promise not to laugh)
definately one button for the following reasons
1/ real estate
2/ attention moving - with 2 buttons you are continually asking the user to move the
focus
as they click the button they are focused on it and can quite easily see the change.
3/ The trick with UI is CONSISTENCY - develop a style and stick to it - if it's quirky
who gives a shit it
is usually an expression of the developers style (32 pages of diatribe on design
in the 20th century edited out here)
regards
Neven
-----Original Message-----
From: Grant Black [SMTP:[EMAIL PROTECTED]]
Sent: Friday, September 03, 1999 2:35 PM
To: Multiple recipients of list delphi
Subject: [DUG]: One button or two
Purely subjective UI question. What do people prefer on a toolbar or
form given that there is some process which can be started and stopped.
(a) Two buttons ie: [Start] [Stop] one of which is always not enabled,
(ie when the process in underway only Stop is enabled)
or
(b) One button which changes - ie [Start] which once the process starts
changes to [Stop]
I suspect from what I re-call of POET and other UI books that (a) is the
best choice as swapping UI around on people is generally considered a
bad thing, but then two buttons take up twice the amount of limited
screen real-estate...
Grant Black
Software Developer
SmartMove (NZ) Ltd
Phone: +64 9 361-0219 extn 719
Fax : +64 9 361-0211
Email: [EMAIL PROTECTED]
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
application/ms-tnef
