mirror of
https://github.com/ProxymanApp/Proxyman.git
synced 2026-04-25 16:15:55 +03:00
[GH-ISSUE #1437] Breakpoint: ambiguity on Cancel and Abort #1431
Labels
No labels
Discussion
Feature request
In Progress...
Plugins
Waiting response
Windows
Windows
bug
duplicate
enhancement
feature
good first issue
iOS
macOS 10.11
question
wontfix
✅ Done
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Proxyman#1431
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @tomisacat on GitHub (Nov 17, 2022).
Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/1437
Originally assigned to: @NghiaTranUIT on GitHub.
Description
When debugging a breakpoint, the meaning of
CancelandAbortis confusing, I would not tell the difference without reading the manual. Would you like to consider other names to help distinguishing between these two actions?@NghiaTranUIT commented on GitHub (Nov 17, 2022):
Let me think the suitable wording 👍
@crankygeek commented on GitHub (Nov 21, 2022):
I run into this too, I always end up clicking Abort. :)
What about "Continue"? That would match Xcode, and may be familiar for users.
Also, I noticed a typo in the Cancel button's tooltip. Won't matter if you change it, but just in case, "Canncel the breakpoint..." Using Version 3.13.0 (31300).
@tomisacat commented on GitHub (Nov 22, 2022):
Continuesounds good.@NghiaTranUIT commented on GitHub (Nov 22, 2022):
Thanks. Let's me update the Cancel button to the Continue button 👍
@NghiaTranUIT commented on GitHub (Nov 23, 2022):
Fix with this Beta build: https://proxyman.s3.us-east-2.amazonaws.com/beta/Proxyman_3.13.0_Rename_Cancel_to_Continue_Breakpoint.dmg
@tomisacat commented on GitHub (Nov 28, 2022):
Thanks for @NghiaTranUIT 's quick response