Bug 101045 - [Sync View] Missing "Select All" shortcut in sync view
Summary: [Sync View] Missing "Select All" shortcut in sync view
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Team (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows All
: P3 normal with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: Platform Team Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 167034 189713 (view as bug list)
Depends on:
Blocks:
 
Reported: 2005-06-21 09:42 EDT by Eugene Kuleshov CLA
Modified: 2019-09-06 16:07 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Eugene Kuleshov CLA 2005-06-21 09:42:26 EDT
"Select All" (Ctrl-A on windows) is one of the most frequently used actions on
any list, tree or text widgets. Please provide this shortcut for Synchronize view.
Comment 1 Michael Valenta CLA 2005-06-21 09:51:33 EDT
Note that, as a workaround of sorts, there are two buttons, Commit All and 
Update All, on the toolbar which help in those two situations.
Comment 2 Eugene Kuleshov CLA 2005-06-21 10:19:18 EDT
Michael, these buttons have no keyboard shortcuts either and can only be invoked
with a mouse. I'm looking for something like: Ctrl-A, Shift-F10, U
Comment 3 Michael Valenta CLA 2006-12-12 13:52:39 EST
*** Bug 167034 has been marked as a duplicate of this bug. ***
Comment 4 Michael Valenta CLA 2007-05-30 08:39:56 EDT
*** Bug 189713 has been marked as a duplicate of this bug. ***
Comment 5 Ed Merks CLA 2007-05-30 09:07:22 EDT
Note that something I often do is selectAll and then unselect some of the things, (because I have projects from other groups in my workspace and sometimes change I make in EMF changes their generated templates) so a commit all button doesn't help for that.
Comment 6 Eclipse Webmaster CLA 2019-09-06 16:07:51 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.