-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Disable all conditions in breakpoints #549 #550
base: master
Are you sure you want to change the base?
Disable all conditions in breakpoints #549 #550
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As commented on the ticket, this only adds more complexity to the menu.
I don't see any reason why anyone would need an extra item for removing conditional breakpoints and why it is so important to get it into the menu.
In the opposite, removing al conditional breakpoints is more dangerous as usual ones because often conditions are non trivial and if lost, need much more time to restore compared to simple breakpoints that can be togled by a single click.
So definitely no.
Okay @iloveeclipse will cancel this then. Thank you |
@iloveeclipse By the way the conditions are not removed they are only disabled. if user wants that condition again the condition will still be available in the text area so it can enabled by the tick option |
@iloveeclipse shall I reopen this ? |
This is extremely confusing. |
Will correct it now. |
Will update the code now. |
Now you are pushed an older commit? It is not on the master branch head as before. |
bacf750
to
394e594
Compare
I have force pushed a new one now. |
Still not on latest master state |
let me check again |
c20f1f4
to
2d7ded5
Compare
75f08dd
to
afa36d2
Compare
Hi @iloveeclipse , had some issues with my git earlier, now its fixed pls check latest commit |
org.eclipse.jdt.debug.ui/ui/org/eclipse/jdt/internal/debug/ui/actions/ActionMessages.properties
Outdated
Show resolved
Hide resolved
...dt.debug.ui/ui/org/eclipse/jdt/internal/debug/ui/actions/RemoveAllCondtionalBreakpoints.java
Outdated
Show resolved
Hide resolved
...dt.debug.ui/ui/org/eclipse/jdt/internal/debug/ui/actions/RemoveAllCondtionalBreakpoints.java
Outdated
Show resolved
Hide resolved
for (IBreakpoint breakpoint : DebugPlugin.getDefault().getBreakpointManager().getBreakpoints()) { | ||
if (breakpoint instanceof JavaLineBreakpoint javaBp) { | ||
if (javaBp.isConditionEnabled()) { | ||
javaBp.setConditionEnabled(false); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure this is the right thing to do. I would expect the breakpoint to be disabled, not the condition on the breakpoint
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Intention of the PR is to provide functionality similar to "Remove All Triggers" in which all triggers in breakpoints will be disabled by preserving the breakpoint enabled/disabled status.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
so for this all conditional check will be disabled. keeping the condition and enabled/disabled status as it is.
...dt.debug.ui/ui/org/eclipse/jdt/internal/debug/ui/actions/RemoveAllCondtionalBreakpoints.java
Outdated
Show resolved
Hide resolved
afa36d2
to
821e5d4
Compare
821e5d4
to
426110f
Compare
This pull request changes some projects for the first time in this development cycle.
An additional commit containing all the necessary changes was pushed to the top of this PR's branch. To obtain these changes (for example if you want to push more changes) either fetch from your fork or apply the git patch. Git patch
Further information are available in Common Build Issues - Missing version increments. |
org.eclipse.jdt.debug.ui/plugin.xml
Outdated
helpContextId="remove_all_breakpoints_action_context" | ||
icon="$nl$/icons/full/elcl16/removeAllConditions.png" | ||
class="org.eclipse.jdt.internal.debug.ui.actions.RemoveAllCondtionalBreakpoints" | ||
menubarPath="breakpointGroupJava" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The right solution would be to add additional separator or group at the platform and contribute new menu to that, so it is not placed in a wrong location. Please try that.
IWorkspaceRunnable runnable = monitor -> { | ||
for (IBreakpoint breakpoint : DebugPlugin.getDefault().getBreakpointManager().getBreakpoints()) { | ||
try { | ||
breakpoint.getMarker().setAttribute(IBreakpoint.ENABLED, breakpoint.isEnabled()); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks like here you change all breakpoints, while above only JavaLimeBreakpoints. This is not OK.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will change it
} | ||
|
||
@Override | ||
protected void initialize() { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why do you need listener? Isn't action state updated on every right click?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have to check that.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Listener is required then only it will update, other right click options have the same too.
Provides additional Action in breakpoints actions for disabling all the conditions set in breakpoints. Will be useful for disabling every conditions in breakpoints by preserving the conditions in the text editor. Enhancement eclipse-jdt#549
50fdd56
to
f2133cf
Compare
This PR provides additional separation and arrangements between Enable/Disable Actions in breakpoints view. New actions can be contributed here. Part of Enhancement #eclipse-jdt/eclipse.jdt.debug#550
This PR provides additional separation and arrangements between Enable/Disable Actions in breakpoints view. New actions can be contributed here. Part of Enhancement #eclipse-jdt/eclipse.jdt.debug#550
This PR provides additional separation and arrangements between Enable/Disable Actions in breakpoints view. New actions can be contributed here. Part of Enhancement #eclipse-jdt/eclipse.jdt.debug#550
This PR provides additional separation and arrangements between Enable/Disable Actions in breakpoints view. New actions can be contributed here. Part of Enhancement #eclipse-jdt/eclipse.jdt.debug#550
This PR provides additional separation and arrangements between Enable/Disable Actions in breakpoints view. New actions can be contributed here. Part of Enhancement #eclipse-jdt/eclipse.jdt.debug#550
Provides additional right click menu option for removing all the conditions set in breakpoints. Will be useful for clearing all the conditions in breakpoints at once.
Enhancement #549
What it does
Provides additional option to remove all conditions
How to test
Author checklist