Bug 88315 - [Sync View] Synchronize View should provide keyboard shortcuts
Summary: [Sync View] Synchronize View should provide keyboard shortcuts
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Team (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform Team Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
: 72850 (view as bug list)
Depends on:
Blocks:
 
Reported: 2005-03-17 07:20 EST by Thorbjørn Ravn Andersen CLA
Modified: 2014-03-17 11:56 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 Thorbjørn Ravn Andersen CLA 2005-03-17 07:20:53 EST
I think it would be nice if the Synchronize view was usable by keyboard alone.

I just tried with 3.1M4 and found that even if I could navigate the tree in the
Synchonize Panel with the arrow keys (and return sent me to another panel), I
could not express my intent to Commit, Override and Update or any other entries
in the Right-Mouse-Click menu without rightmouseclicking.
Comment 1 Michael Valenta CLA 2005-03-30 11:08:55 EST
*** Bug 72850 has been marked as a duplicate of this bug. ***
Comment 2 Eugene Kuleshov CLA 2005-03-30 11:40:59 EST
Operations such as commit/update/etc can be called from a context menu
(Shift-F10). You can even change view layout and mode in/out/conflicts and
flat/tree/compressed from view menu (Ctrl-F10)

However you can start synchronization on currently selected working set or
switch to another working set that is already pinned to Synchronize view (there
is an icon with drop down list on Synchronize view toolbar).

Also you can't turn "Change Sets" mode on and off without mouse.

PS: Michael, I do believe that 72850 had more details.
Comment 3 Michael Valenta CLA 2005-04-07 16:10:36 EDT
We'll make sure to look in bug 72850 when this bug is addressed to make sure 
we've covered all the cases. Unfortunately, unless priorities change, there 
isn't time in 3.1 to address this issue.