You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While this new checkbox is checked the user is asked whether or not he or she wants to remove the breakpoint when he or she clicks on the "remove" button.
This can be useful for users who wants to disable, but not remove, a breakpoint but his or her hand slips and he or she both accidentally and mistakenly clicks on the "remove" button instead and then he or she has to waste his or her time to add this breakpoint again with the controls on the bottom of the Breakpoints window or tab.
If the dialog appears instead of just removing the breakpoint the user can click on the "No" button if he or she doesn't want to remove the breakpoint but just disable it.
Same when the user wants to enable a breakpoint but not remove it.
If there are many breakpoints that the user wants to quickly remove them and this dialog can delay him or her, waste his or her time, or even screw him or her then the user simply unchecks the new checkbox before starting to remove all the breakpoints that he or she wants to remove by just clicking on many remove buttons.
Unchecking the new checkbox before starting to remove many breakpoints consumes just a little time, energy and effort but not a lot of.
Since there are situations where this is good to have this new checkbox checked and situations where this is good to have this new checkbox unchecked then do not hardcode to always show this dialog.
Hardcode to always show this dialog before removal of any breakpoint is just a terrible idea and stupid act.
If you really dislike checkboxes so much then another possible solution to the above described problem that does not require to add a new checkbox to the Breakpoints window or tab at all is to add more free space between the remove and the enable/disable buttons so that both the remove and the enable/disable buttons are more further away from each other.
Thus even if the hand of the user slips still he or she won't accidentally or mistakenly click on the remove button when he or she wants to either enable or disable an existing breakpoint but not remove it at all.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
While this new checkbox is checked the user is asked whether or not he or she wants to remove the breakpoint when he or she clicks on the "remove" button.
This can be useful for users who wants to disable, but not remove, a breakpoint but his or her hand slips and he or she both accidentally and mistakenly clicks on the "remove" button instead and then he or she has to waste his or her time to add this breakpoint again with the controls on the bottom of the Breakpoints window or tab.
If the dialog appears instead of just removing the breakpoint the user can click on the "No" button if he or she doesn't want to remove the breakpoint but just disable it.
Same when the user wants to enable a breakpoint but not remove it.
If there are many breakpoints that the user wants to quickly remove them and this dialog can delay him or her, waste his or her time, or even screw him or her then the user simply unchecks the new checkbox before starting to remove all the breakpoints that he or she wants to remove by just clicking on many remove buttons.
Unchecking the new checkbox before starting to remove many breakpoints consumes just a little time, energy and effort but not a lot of.
Since there are situations where this is good to have this new checkbox checked and situations where this is good to have this new checkbox unchecked then do not hardcode to always show this dialog.
Hardcode to always show this dialog before removal of any breakpoint is just a terrible idea and stupid act.
If you really dislike checkboxes so much then another possible solution to the above described problem that does not require to add a new checkbox to the Breakpoints window or tab at all is to add more free space between the remove and the enable/disable buttons so that both the remove and the enable/disable buttons are more further away from each other.
Thus even if the hand of the user slips still he or she won't accidentally or mistakenly click on the remove button when he or she wants to either enable or disable an existing breakpoint but not remove it at all.
Beta Was this translation helpful? Give feedback.
All reactions