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
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee=Noneclosed_at=<Date2015-08-07.23:10:33.706>created_at=<Date2015-08-07.14:16:34.792>labels= ['expert-IDLE', 'type-feature']
title='visual margin indicator for breakpoints in IDLE'updated_at=<Date2015-08-07.23:10:33.705>user='https://github.com/roseman'
Right now breakpoints can only be set/cleared by using a context menu on a line in the editor. I discovered this entirely by reading through the bug database, as right-click doesn't work on OS X (bpo-24801).
Some other tools use an indicator (e.g. stop sign) in the left margin, which can be toggled on and off by a simple click. This could exist in conjunction with line numbering (bpo-17535)
bpo-24801 needs to be fixed so we can depend on right clicking. I think SET and CLEAR should be replace by TOGGLE (bpo-22083). The patch for bpo-17535 already includes marking breakpoints in the margin. I am opposed to a putting a symbol on every line. Too noisy and too confusing to beginners for an advanced feature. There are other things that could be added to a line-number context menu, such as cutting or copying a line without having to drag select it (which is too easy to mess up).
oh agree, definitely don't want a symbol on every line. i was already thinking implementation where you'd probably have an object matching the background for hit detection! :-)
but yes, visually nothing there but empty space when there isn't a breakpoint, and a symbol there when the breakpoint is set
I believe one of Saimadhav's original patches used a symbol. I suggested color highlighting instead, and it seems to work better. In any case, debating such details is part of an issue.
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: