Bug 67031 - [Dialogs] Eclipse dialogs do not respect mouse's Smart Move setting
Summary: [Dialogs] Eclipse dialogs do not respect mouse's Smart Move setting
Status: RESOLVED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows XP
: P4 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Tod Creasey CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 20563 (view as bug list)
Depends on:
Blocks:
 
Reported: 2004-06-14 12:54 EDT by Dani Megert CLA
Modified: 2005-01-06 14:35 EST (History)
2 users (show)

See Also:

Attachments
mouse settings dialog (8.15 KB, image/png)
2004-06-14 12:54 EDT, Dani Megert CLA 		no flags Details
View All 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 Dani Megert CLA 2004-06-14 12:54:34 EDT 
3.0 RC2 (and previous builds)

I've enabled "Smart Move" in my mouse settings which causes the mouse cursor to
jump to the highlighted (default) button of newly opened dialogs (see attached
picture of mouse settings dialog). This does not work with Eclipse dialogs.
Given the platform centric approach I would expect this to work.
Comment 1 Dani Megert CLA 2004-06-14 12:54:57 EDT 
Created attachment 12053 [details]
mouse settings dialog
Comment 2 Veronika Irvine CLA 2004-06-16 11:39:32 EDT 
This will only work if the default button is a direct child of the shell (no 
intermediate parents). We tried to work around this in the past and failed.  A 
C application has the same restrictions.

Reassigning to UI to consider making the default buttons children of teh shell.
Comment 3 Tod Creasey CLA 2004-06-16 15:03:24 EDT 
Not for 3.0
Comment 4 Tod Creasey CLA 2004-06-28 11:27:40 EDT 
Reopening now that 3.0 has shipped
Comment 5 Tod Creasey CLA 2005-01-06 11:24:39 EST 
To make this work we would break pretty much every existing dialog unless the OS
relaxes the parenting restriction.
Comment 6 Tod Creasey CLA 2005-01-06 11:41:41 EST 
*** Bug 20563 has been marked as a duplicate of this bug. ***