Bug 190867 - [Commands] Problems invoking object contribution action via Ctrl+3
Summary: [Commands] Problems invoking object contribution action via Ctrl+3
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.3   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-06-04 14:47 EDT by Nick Edgar CLA
Modified: 2019-09-06 15:36 EDT (History)
2 users (show)

See Also:


Attachments
Screen shot of error dialog on Linux. (27.58 KB, image/png)
2007-06-04 14:48 EDT, Nick Edgar CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Nick Edgar CLA 2007-06-04 14:47:29 EDT
3.3 M7

- start our product in a new eclipse workspace
- from the Welcome page, invoke the "Show Pending Changes" command via Quick Access (Ctrl+3)
- on Linux it fails with the "There is no handler to execute..." scary error dialog (see screen shot)
- on WinXP it runs the associated handler, but this does not run as expected since the selection is inappropriate (it's an object contribution against ResourceMapping with adaptable=true)

Expectation: The command doesn't show up in Quick Access if it has no appropriate handler.  If there is a matching handler, it gets the adapted selection (from the appropriate selection provider, i.e. the one passed to registerContextMenu).
Alternatively, show all commands, but give a less scary dialog saying the command it's not currently available.  But the selection should still the right one.

Back link to our bug DB: #25116
Comment 1 Nick Edgar CLA 2007-06-04 14:48:47 EDT
Created attachment 70010 [details]
Screen shot of error dialog on Linux.
Comment 2 Boris Bokowski CLA 2007-06-04 16:10:40 EDT
See bug 185899 for the scary dialog.
Comment 3 Eclipse Webmaster CLA 2019-09-06 15:36: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.