Bug 152110 - [key binding] Provide command for double-click strategy
Summary: [key binding] Provide command for double-click strategy
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Text (show other bugs)
Version: 3.2   Edit
Hardware: All All
: P5 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform-Text-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2006-07-28 04:00 EDT by Uwe Voigt CLA
Modified: 2019-09-06 15:37 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 Uwe Voigt CLA 2006-07-28 04:00:31 EDT
Even if it sounds silly to invoke a double click strategy by a key sequence because normally no one double clicks on the keyboard it could be helpful to have an action wrapping that functionality. Then one can map that action to a key sequence and doesn't have to always grab the mouse to select some text.
Comment 1 Paul Webster CLA 2006-07-28 11:12:14 EDT
Isn't it tied to Enter if the selection has focus?

PW
Comment 2 Uwe Voigt CLA 2006-07-28 12:02:08 EDT
I have looked at the code and saw that the double click strategy is rather private to text viewers. Since the editor is the better place to put actions in I believe this would introduce too much change. 
The "expand selection to next element" almost fits the functionality of the double click at braces with the slight difference that it also selects block beginning and block end curly braces.
See it as a short monolog and close.
Comment 3 Paul Webster CLA 2006-09-28 11:01:53 EDT
There are currently no plans to work on this feature.

PW
Comment 4 Denis Roy CLA 2007-06-22 09:33:30 EDT
Changes requested on bug 193523
Comment 5 Eclipse Webmaster CLA 2019-09-06 15:37:43 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.