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

Bug 339230

Summary: Editor position of 'error' keeps focus in 'Project Explorer'
Product: [Tools] CDT Reporter: Dirk Wibben <dirk.wibben>
Component: cdt-buildAssignee: cdt-build-inbox <cdt-build-inbox>
Status: RESOLVED DUPLICATE QA Contact: Andrew Gvozdev <angvoz.dev>
Severity: minor    
Priority: P3 CC: aleherb+eclipse, cdtdoug
Version: 7.0.2   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard:

Description Dirk Wibben CLA 2011-03-08 09:57:17 EST 
Build Identifier: 20100917-0705 (CDT 7.0.2.201102110609)

I have several projects in a workspace with all but one in state 'closed'. I use the 'Project Explorer' view (PE) for this.
In the solely opened project I do a 'Build', which creates an 'error'. This error is indicated correctly in the Console.
After I selected the error via double-click or clicking the 'down' arrow, the focus in the PE turns to the source file containing the error (so far Okay).
When I then try to click on a closed project in the PE, the focus immediately returns to the error module. I can't select a closed project.
When I clear the Console, everything is fine again.

Reproducible: Always

Steps to Reproduce:
See 'Details'.
Comment 1 Anton Leherbauer CLA 2011-03-08 09:59:39 EST 
This sounds like build console issue.
Comment 2 Andrew Gvozdev CLA 2011-03-08 10:42:15 EST 
As a workaround, you could disable synchronization of CDT console with editor.

*** This bug has been marked as a duplicate of bug 306338 ***
Comment 3 Dirk Wibben CLA 2011-03-09 02:27:21 EST 
It is not a 'daily base' issue, therefore I can live with it so far.

But why is this bug a duplicate of the bug 306338? I don't see any similarity. Maybe you have chosen the wrong duplicate bug?

Regards
Dirk
Comment 4 Andrew Gvozdev CLA 2011-03-09 07:31:31 EST 
(In reply to comment #3)
> But why is this bug a duplicate of the bug 306338? I don't see any similarity.
> Maybe you have chosen the wrong duplicate bug?
There is a similarity in the bug number. Thanks for pointing it out.

*** This bug has been marked as a duplicate of bug 306388 ***