Bug 261429 - some Eclipse dialogues collides with X-Mouse
Summary: some Eclipse dialogues collides with X-Mouse
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 3.4.1   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Steve Northover CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-01-18 15:00 EST by Susanne Jonda CLA
Modified: 2019-09-06 16:03 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 Susanne Jonda CLA 2009-01-18 15:00:13 EST
Build ID: M20080911-1700

Steps To Reproduce:
I'm a long time user of the X-Mouse option in Microsofts Tweak UI for Windows XP. Two of the applications I use have problems with this mouse behaviour and unfortunately Eclipse is one of them.

How to activate "X-Mouse":
- download and install Tweakui from Microsoft's Windows XP PowerToys homepage
- start Programs->PowerToys for Windows XP->Tweak UI
- in the new window open section Mouse->X-Mouse
- make selections:
  . [X] Activation follows mouse
  . [ ] Autoraising when activating
  (autoraising not selected!)
Now you have activated the activation style often used on X-Windows (Unix) systems. It will give the input focus to the window containing the mouse 
pointer without having to click the window first.


Now when calling Quick Type Hierarchy via menu item or Ctrl+T I only see a short yellow flicker if the mouse isn't where the dialogue comes up. No problem with X-Mouse off.
Strangely the it's the same when calling Quick Outline via the menu but when using the keyboard shortcut (Ctrl+O) it works like it should (i.e. the dialogue sticks).

No problem at all with Quick Fix tooltips or so.

More information:
Comment 1 Eclipse Webmaster CLA 2019-09-06 16:03:33 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.