Bug 469929 - [Ruler] "Disable Breakpoint" and "Breakpoint Properties" should only be visible if there is a breakpoint
Summary: [Ruler] "Disable Breakpoint" and "Breakpoint Properties" should only be visib...
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 4.5   Edit
Hardware: All All
: P5 minor (vote)
Target Milestone: ---   Edit
Assignee: Platform-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on: 470069
Blocks:
  Show dependency tree
 
Reported: 2015-06-11 08:23 EDT by Lars Vogel CLA
Modified: 2020-01-30 14:54 EST (History)
2 users (show)

See Also:


Attachments
Screenshot (16.73 KB, image/png)
2015-06-11 08:23 EDT, Lars Vogel CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Lars Vogel CLA 2015-06-11 08:23:55 EDT
Created attachment 254331 [details]
Screenshot

The entry "Disable Breakpoint" should IMHO only be there if the ruler contains a breakpoint. 

I think it is reasonable to expect that a function available for an object is only present if the object is present.
Comment 1 Dani Megert CLA 2015-06-11 08:41:11 EDT
I agree, but it isn't possible to hide contributed ruler actions. This would first have to be implemented in Platform Text.
Comment 2 Lars Vogel CLA 2015-06-11 10:15:45 EDT
(In reply to Dani Megert from comment #1)
> I agree, but it isn't possible to hide contributed ruler actions. This would
> first have to be implemented in Platform Text.

Should be create a bug for that and mark this one as dependent on it?
Comment 3 Dani Megert CLA 2015-06-11 10:29:30 EDT
(In reply to Lars Vogel from comment #2)
> (In reply to Dani Megert from comment #1)
> > I agree, but it isn't possible to hide contributed ruler actions. This would
> > first have to be implemented in Platform Text.
> 
> Should be create a bug for that and mark this one as dependent on it?

You can, if you think someone is going to work on that, otherwise please close this one again since it's not solvable without that.
Comment 4 Eclipse Genie CLA 2020-01-30 14:54:00 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. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. 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.