This is the mail archive of the
insight@sources.redhat.com
mailing list for the Insight project.
Re: Modal dialogs again
- To: Jim Ingham <jingham at apple dot com>
- Subject: Re: Modal dialogs again
- From: Tom Tromey <tromey at redhat dot com>
- Date: 21 May 2001 23:43:00 -0600
- Cc: Keith Seitz <keiths at cygnus dot com>, Insight Maling List <insight at sources dot redhat dot com>
- References: <200105211747.f4LHlvk26760@scv2.apple.com>
- Reply-To: tromey at redhat dot com
>>>>> "Jim" == Jim Ingham <jingham@apple.com> writes:
Jim> Error messages like "Couldn't connect to target board" or "Your
Jim> program just crashed" certainly should be modal, and SHOULD be
Jim> dialogs.
I don't think these are similar enough to be treated similarly.
For the first, I agree, especially if there is some reason attached so
that figuring out the why of the failure to connect might reasonably
begin.
For the second, I think there are already plenty of other indications
that a program crashed. For instance the buttons ought to change
state (you can no longer "Next" a crashed program). The dialog that
pops up for this never fails to annoy. Or, to look at it another way,
shouldn't we also pop up a dialog when we hit a temporary breakpoint?
Or when a watchpoint is taken? Or a signal handled?
Jim> 2) Configuration panels:
Jim> Does is happen right when you change one of the combo boxes?
Unfortunately Insight already suffers from confusion on this issue.
Sometimes I think the answer is yes, sometimes no. This is worse than
making the "wrong" choice for the modality of the dialog (or, rather,
confusion *is* the only wrong choice :-).
Tom