Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 329458 - [EditorMgmt] Editor is not automatically set as the active part on startup
Summary: [EditorMgmt] Editor is not automatically set as the active part on startup
Status: RESOLVED WORKSFORME
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.0   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact: Eric Moffatt CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-11-04 12:49 EDT by Remy Suen CLA
Modified: 2014-02-26 07:09 EST (History)
4 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Remy Suen CLA 2010-11-04 12:49:19 EDT 
In 3.x, if we have an editor open, it will be activated on startup even if it was not the originally active part.

See bug 328703 for the case with views.

Thread [main] (Suspended (breakpoint at line 955 in EditorManager$5))	
	EditorManager$5.runWithException() line: 955	
	EditorManager$5(StartupThreading$StartupRunnable).run() line: 31	
	RunnableLock.run() line: 35	
	UISynchronizer(Synchronizer).runAsyncMessages(boolean) line: 134	
	Display.runAsyncMessages(boolean) line: 4059	
	Display.readAndDispatch() line: 3678	
	IDEWorkbenchAdvisor(WorkbenchAdvisor).openWindows() line: 803	
	Workbench$31.runWithException() line: 1566	
	Workbench$31(StartupThreading$StartupRunnable).run() line: 31	
	RunnableLock.run() line: 35	
	UISynchronizer(Synchronizer).runAsyncMessages(boolean) line: 134	
	Display.runAsyncMessages(boolean) line: 4059	
	Display.readAndDispatch() line: 3678	
	Workbench.runUI() line: 2537	
	Workbench.access$4(Workbench) line: 2427	
	Workbench$7.run() line: 670	
	Realm.runWithDefault(Realm, Runnable) line: 332	
	Workbench.createAndRunWorkbench(Display, WorkbenchAdvisor) line: 663	
	PlatformUI.createAndRunWorkbench(Display, WorkbenchAdvisor) line: 149	
	IDEApplication.start(IApplicationContext) line: 115
Comment 1 Remy Suen CLA 2011-01-11 16:31:58 EST 
The auto-activation should mean that Ctrl+W should work immediately. See bug 328496 comment 1.
Comment 2 Eric Moffatt CLA 2013-12-10 15:37:58 EST 
M4 is done...
Comment 3 Dani Megert CLA 2014-01-24 05:49:49 EST 
More important is bug 348954.
Comment 4 Dani Megert CLA 2014-02-26 07:09:37 EST 
I think it's fair to keep the focus on the part that was active when closing the workbench.