Bug 227155 - Support PageSwitcher commands
Summary: Support PageSwitcher commands
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Team (show other bugs)
Version: 3.4   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform Team Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-04-15 11:46 EDT by Markus Keller CLA
Modified: 2019-09-06 15:34 EDT (History)
1 user (show)

See Also:


Attachments
Fix (8.79 KB, text/plain)
2008-04-15 11:46 EDT, Markus Keller CLA
no flags Details
Fix 2 (10.62 KB, patch)
2008-04-16 06:48 EDT, Markus Keller CLA
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Markus Keller CLA 2008-04-15 11:46:44 EDT
Created attachment 96102 [details]
Fix

HEAD

The Synchronize and the History views should support the new page switcher commands from bug 146623. To test the patch, you have to bind the Next Page and Previous Page commands, e.g. to Alt+PageDown / Alt+PageUp.

The patch also
- binds the 'Link with Editor and Selection' action to the new command
- sets the action definition IDs of the Link and Refresh toolbar buttons, such that their tooltips can show the current key binding
Comment 1 Markus Keller CLA 2008-04-16 06:48:17 EDT
Created attachment 96241 [details]
Fix 2

Oops, the previous attachment missed a file and was not marked as patch.
Comment 2 Tomasz Zarna CLA 2008-06-20 10:07:23 EDT
I applied the patch and it works like a charm, with one exception, I can't see the key binding for the Link button. The binding I used is "Alt+L" and it works fine, but it doesn't show up in the tooltip.
Comment 3 Markus Keller CLA 2008-12-11 11:09:40 EST
The tooltip works fine for me with I20081211-0100. Even if it doesn't work for you, could you still commit the rest and file a new bug with steps that don't work?
Comment 4 Eclipse Webmaster CLA 2019-09-06 15:34:57 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.