https://bugs.kde.org/show_bug.cgi?id=462898

            Bug ID: 462898
           Summary: [wish] Better visual indication of compilation
                    warnings/errors existence
    Classification: Applications
           Product: kdevelop
           Version: unspecified
          Platform: unspecified
                OS: All
            Status: REPORTED
          Severity: wishlist
          Priority: NOR
         Component: Output Views
          Assignee: kdevelop-bugs-n...@kde.org
          Reporter: a.sum.d...@gmail.com
  Target Milestone: ---

Created attachment 154492
  --> https://bugs.kde.org/attachment.cgi?id=154492&action=edit
The "build" tool view in current form

SUMMARY
I suggest to improve visual indication of the fact that warnings/errors
occurred while building a project. Colouring warning/error lines in the "Build"
tool view is insufficient.

DETAILED DESCRIPTION
When building a project, we can observe compiler output in the "Build" tool
view. Warning/error lines are coloured yellow/red and we can jump from one to
another using the arrow buttons located on the toolbar of the tool view.
However, it can be easy to miss the fact that any warnings/errors actually
occurred, especially warnings when compilation process is long and outputs many
lines. I suggest to add some visual indication of the fact that warnings/errors
occurred and perhaps indication of their count.

IMPLEMENTATION IDEAS
* grey out (disable) the first/prev/next/last arrow buttons if there are no
warnings/errors
* show somewhere an icon and/or a label indicating warnings/errors existence
and perhaps their count:
 - on the button that toggles the "Build" tool view (the advantage is that it
would be visible even if we switch to other tool view)
 - on the toolbar of the "Build" tool view
* add to the toolbar of the "Build" tool view new buttons for quick filtering
by warnings/errors, their appearance would indicate warnings/errors existence
i.e. greyed out or not

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to