[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kdevelop-bugs
Subject:    [Bug 125850] New: [Usability] Project run and debug options for separate terminal are inconsistent/c
From:       kdevelop-bugs-admin () barney ! cs ! uni-potsdam ! de
Date:       2006-04-19 0:24:41
Message-ID: 20060419022439.125850.dschuff () purdue ! edu
[Download RAW message or body]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=125850         
           Summary: [Usability] Project run and debug options for separate
                    terminal are inconsistent/confusing
           Product: kdevelop
           Version: 3.3.1
          Platform: unspecified
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: wishlist
          Priority: NOR
         Component: general
        AssignedTo: kdevelop-bugs kdevelop org
        ReportedBy: dschuff purdue edu


Version:           3.3.1 (using KDE 3.5.1, Debian Package 4:3.5.1-2 \
                (testing/unstable))
Compiler:          Target: x86_64-linux-gnu
OS:                Linux (x86_64) release 2.6.16-1-amd64-k8-smp

For both debugging and normal running, there are options to use a separate terminal \
for application I/O. They have the same purpose are intended to do the same thing, \
however, there are 2 problems:

First, there are 2 different names for the same thing: in the Run Options, the \
checkbox is labelled "Start in external terminal", and in the Debugger options, it's \
labelled "Enable separate terminal for application IO". This was enough to confuse a \
user who is an experienced Linux user, and for whom "terminal" is not a familiar and \
obvious term. They should have the same name (the latter name is more clear IMO, but \
you could maybe even do better)

Second, the options actually do different things. the Run option executes a shell \
command which runs the program, echoes "Press enter to continue" and then reads a \
dummy line and exits. The debug command does not do this, and so closes the terminal \
immediately without warning, and without giving the user any opportunity to read the \
output... so I would actually classify this behavior as a bug.


[prev in list] [next in list] [prev in thread] [next in thread]