mirror of
https://github.com/ProxymanApp/proxyman-windows-linux.git
synced 2026-04-27 00:45:55 +03:00
[GH-ISSUE #362] Proxyman it using F5 and prevents other applications such as notepad++ or visualstudio from using this F5 key. #361
Labels
No labels
Linux
bug
enhancement
enhancement
pull-request
question
✅ Done
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/proxyman-windows-linux#361
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 @jagreen03im on GitHub (Feb 2, 2024).
Original GitHub issue: https://github.com/ProxymanApp/proxyman-windows-linux/issues/362
Originally assigned to: @kics223w1 on GitHub.
Description
Steps to Reproduce
Open proxyman
Open notepad++ press F5 nothing happens
Close proxymand
inside notepad++ press F5 see a dialog open to Run.
Current Behavior
Proxyman is intercepting F5 key presses. Note that visual studio uses F5 but still doesn't prevent notepad++ from using F5 with that application is active. So Proxyman is not only using F5 but owning that key preventing other apps from using F5.
Expected Behavior
If proxyman is opened anyother application should be able to respond to the F5 keypress.
Environment
@kics223w1 commented on GitHub (Feb 3, 2024):
Before the release of 2.10.0, I discovered that users can press
F5to refresh the application. So I added the code to disable it. I didn't realize that it would affect the other applications. I'll revert this code and use another approach in the next release.@Inrego commented on GitHub (Feb 7, 2024):
Thank god it's just a bug. I just started using Proxyman and noticed this behavior. I was looking through preferences to find key bindings so I could disable the hotkey in Proxyman, but to no avail. Looking forward for the next release with this fixed!
@NghiaTranUIT commented on GitHub (Feb 7, 2024):
Thanks, the bug is fixed in the main branch, we will release this week 👍