Received: (at submit) by bugs.debian.org; 4 Feb 1997 03:42:28 +0000 Received: (qmail 11006 invoked from network); 4 Feb 1997 03:42:26 -0000 Received: from gigan.extern.ucsd.edu (root@137.110.78.121) by master.debian.org with SMTP; 4 Feb 1997 03:42:26 -0000 Received: from gigan (gobbel@localhost [127.0.0.1]) by gigan.extern.ucsd.edu (8.8.5/8.8.5) with SMTP id TAA01781; Mon, 3 Feb 1997 19:36:19 -0800 Sender: gobbel@cogsci.ucsd.edu Message-ID: <32F6AEB2.373C102@cogsci.ucsd.edu> Date: Mon, 03 Feb 1997 19:36:18 -0800 From: Randy Gobbel Organization: Cognitive Science Dept., UCSD X-Mailer: Mozilla 3.01Gold (X11; U; Linux 2.0.27 i686) MIME-Version: 1.0 To: submit@bugs.debian.org Subject: dselect: hyperjump into conflict screen is poor UI design Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Package: dpkg Version: 1.4.0.7 There is no reason for dselect to jump straight into the conflict resolution screen as soon as the user types "+" (or whatever). This is jarring, confusing, and not even the best way to deal with the situation. Much better would be to put some sort of flag on the screen saying "conflicts". Oftentimes, I *know* that package X requires package Y, but package Y is just farther down in the list. If dselect wouldn't be so #$* hyper, I would get to the required package, mark it, and maybe I wouldn't have to see the hated conflict screen at all. Bottom line: dselect should only put up the conflict screen at the end of the "select" session. It should deal with all conflicts then, and optionally allow the user to go back to "select" mode at that point if need be. I think this would go a long way toward easing Debian users' trauma in using dselect. -Randy