Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 367109 - [markers] actions available in empty view: select all, show in
Summary: [markers] actions available in empty view: select all, show in
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.7.1   Edit
Hardware: All All
: P3 trivial (vote)
Target Milestone: ---   Edit
Assignee: Platform-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-19 12:30 EST by Helmut J. Haigermoser CLA
Modified: 2019-11-13 15:27 EST (History)
0 users

See Also:

Attachments
List of enabled actions in an empty tasks view (17.46 KB, image/png)
2011-12-19 12:31 EST, Helmut J. Haigermoser CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Helmut J. Haigermoser CLA 2011-12-19 12:30:10 EST 
Build Identifier: 

The markers views bookmarks, tasks and problems all share similar context menu actions:
"Select All" and "Show In"

These two actions seem to be context sensitive but despite that show up when there is no content within the view, this should be changed to grey out actions that don't make sense at the moment.

Note that the tasks view has another such action:
"Delete Completed Tasks", that one should be greyed out as well...



Reproducible: Always

Steps to Reproduce:
1. Open empty tasks, bookmarks or problems view
2. Open context menu of the view
3. Enabled actions are found
Comment 1 Helmut J. Haigermoser CLA 2011-12-19 12:30:48 EST 
CQ:WIND00085118

*setting Version to 3.7.1*

Please let me know in case you need any more information! :)
Helmut
Comment 2 Helmut J. Haigermoser CLA 2011-12-19 12:31:57 EST 
Created attachment 208571 [details]
List of enabled actions in an empty tasks view
Comment 3 Eclipse Genie CLA 2019-11-13 15:27:44 EST 
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.

--
The automated Eclipse Genie.