Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 314844

Summary:	CDT Build Console: Add button to jump to first error
Product:	[Tools] CDT	Reporter:	Axel Mueller <aegges>
Component:	cdt-build	Assignee:	cdt-build-inbox <cdt-build-inbox>
Status:	REOPENED ---	QA Contact:	Jonah Graham <jonah>
Severity:	enhancement
Priority:	P3	CC:	malaperle
Version:	7.0
Target Milestone:	---
Hardware:	PC
OS:	All
Whiteboard:

Description Axel Mueller

2010-05-28 07:29:48 EDT

Build Identifier: 

The new build console has two buttons to jump to the next and previous error/warning. It would be very helpful to have a button to jump to the very first error. Very often, the first error (e.g. missing semicolon or include) leads to dependent errors.

Reproducible: Always

Comment 1 Andrew Gvozdev

2010-05-28 09:27:36 EDT

After the build is finished pressing "Next" button navigates to the first error (problem marker). Is it good enough?

Comment 2 Axel Mueller

2010-05-28 11:02:12 EDT

(In reply to comment #1)
> After the build is finished pressing "Next" button navigates to the first error
> (problem marker). Is it good enough?
I did not know. It is not really obvious :( But I can live with it.

Comment 3 Axel Mueller

2010-05-31 09:28:57 EDT

After thinking a little bit about comment #1 and using it I guess we can close this bug. I am fine with the workflow.

Comment 4 Axel Mueller

2010-06-17 04:59:45 EDT

I will reopen this bug because I noticed that having a button that jumps to the first *error* is very helpful. As mentioned in comment #1 the Next button navigates to the first problem marker. But if your application generates a lot of warnings *before* the first error the Next button is pretty useless.

Comment 5 Andrew Gvozdev

2010-06-17 12:27:34 EDT

I agree and I would argue that it would be useful to use Next/Previous buttons to jump on errors only. For example we could have 3 options with a switch on the toolbar:
1. Jumping between errors only
2. Jumping between errors and warnings
3. Jumping between all markers (errors, warnings and inros)

See also bug 307211 requesting to highlight them differently on the console.

Comment 6 Axel Mueller

2010-06-20 13:17:51 EDT

(In reply to comment #5)
> I agree and I would argue that it would be useful to use Next/Previous buttons
> to jump on errors only. For example we could have 3 options with a switch on
> the toolbar:
> 1. Jumping between errors only
> 2. Jumping between errors and warnings
> 3. Jumping between all markers (errors, warnings and inros)
Just to clarify things. We need two things:
1) an additional button to jump for the first error
2) a kind of filter for the Next/Previous buttons (as described above)

Comment 7 Marc-André Laperle

2010-09-22 19:00:39 EDT

(In reply to comment #5)
> I agree and I would argue that it would be useful to use Next/Previous buttons
> to jump on errors only. For example we could have 3 options with a switch on
> the toolbar:
> 1. Jumping between errors only
> 2. Jumping between errors and warnings
> 3. Jumping between all markers (errors, warnings and inros)

Not sure if this is what you mean, but it could work like the Next/Previous Annotation buttons.

Comment 8 Axel Mueller

2010-09-23 03:00:33 EDT

(In reply to comment #7)
> (In reply to comment #5)
> > I agree and I would argue that it would be useful to use Next/Previous buttons
> > to jump on errors only. For example we could have 3 options with a switch on
> > the toolbar:
> > 1. Jumping between errors only
> > 2. Jumping between errors and warnings
> > 3. Jumping between all markers (errors, warnings and inros)
> 
> Not sure if this is what you mean, but it could work like the Next/Previous
> Annotation buttons.
That sounds good for me.
Perhaps I will find some time in the next weeks to have a look at this (if no one else wants to do this, of course).