Community
Participate
Working Groups
3.0 M3 The Synchronize View has actions that appear in the view's tollbar. They have keybindings to the NEXT, PREVIOUS global handlers. They don't appear in the UI unless I comment out the code to register them with the keybinding service and the global handler. Pre-3.0 this was working just fine. I suspect the new command stuff is to blame... All other actions, not registered with the service are shown correctly. Because of this the select next/previous toolbar items in the sync view are not shown.
doug please look at this one right away.. thanks.
from a conversation with jean-michel: Lines 49, 50, 53 and 54 of NavigateAction (org.eclipse.team.ui) can be commented out to get the two buttons to appear in the (new) Synchronize view toolbar. If those lines aren't commented out, then the buttons do not appear.
Created attachment 6079 [details] Patch to plugin.xml and plugin.properties The commands weren't defined.
I'm not sure if this is a regression in functionality over the old architecture. (I just started here a couple of months ago.) If it is, punt the bug back at Chris.
Thanks Doug. that worked. It would probably be nice if something was added to the log when an action is being ignored for whatever reason. It would help plugin developers track down problems like this without having to raise a bug :) An in this particular case, maybe allow the action to be shown but disable the keybdings?
fixed.
not actually fixed in terms of logging information, i meant 'invalid' as doug provided the solution without changing code related to this bug. that being said, i'm reopening this one to review during m5 to cover the logging case.
Reassigning to Platform-UI-Inbox (I left IBM 18 months ago..)
Moving Dougs bugs
Assigning to component owner PW
The change is connected to Team UI component. I will reassign to the Team inbox Daniel
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. If the bug is still relevant, please remove the stalebug whiteboard tag.
