Bug 170851 - [WorkbenchLauncher] [KeyBindings] unwanted text entered when starting Eclipse
Summary: [WorkbenchLauncher] [KeyBindings] unwanted text entered when starting Eclipse
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.3   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-01-17 20:02 EST by Walter Harley CLA
Modified: 2019-09-06 15:38 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Walter Harley CLA 2007-01-17 20:02:37 EST
Sorry if this is a dup, I searched and didn't find anything.

I click on a start icon to launch Eclipse, and then while it is starting up, I may continue typing in some other application (such as email).  Eclipse chugs away in the background and then eventually pops to the foreground.  When that happens, it often seems to have grabbed the last few keystrokes of what I was typing, and it then inserts them at the start of whatever source file editor happens to be open in my workspace.  This causes the file to contain a compile error, be out of sync with CVS, and so forth; if I'm lucky, I notice it in time.

I can imagine two fixes: 

  1. don't jump to the foreground if another app has the focus when the Eclipse main window is created (this works because the Workspace Launcher grabs focus from whatever had it before, so if something else has focus it must have gotten it after the launcher was OK'd); 

  2. discard keyboard input from when the main window is created until the app is done being launched.
Comment 1 Boris Bokowski CLA 2009-11-26 16:33:27 EST
Prakash is now responsible for watching bugs in the [WorkbenchLauncher] component area.
Comment 2 Eclipse Webmaster CLA 2019-09-06 15:38:23 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.