Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Renaming a Watch Removes Spaces #3320

Open
utkonos opened this issue Mar 6, 2024 · 2 comments
Open

Renaming a Watch Removes Spaces #3320

utkonos opened this issue Mar 6, 2024 · 2 comments
Labels
bug The issue describes a bug. It does not mean the bug has been reproduced by a developer.

Comments

@utkonos
Copy link

utkonos commented Mar 6, 2024

Operating System

Windows Server 2022 21H2 20348.169

x64dbg Version

Feb 19 2024

Describe the issue

The original name of a Watch contains a space. Example: Watch 12. Editing the name to change the number results in an unexpected name due to the space being removed. Changing this example to Watch 11 results in the name Watch11.

Steps to reproduce

  1. Create a new watch
  2. Change the number of the watch to a different number
  3. Observe name saved with space removed in Watch tab.

Attachments

image
@utkonos utkonos added the bug The issue describes a bug. It does not mean the bug has been reproduced by a developer. label Mar 6, 2024
mrexodia added a commit that referenced this issue Mar 7, 2024
@mrexodia
Properly escape the command arguments for the WatchView
34b1d96 
Closes #3320
@utkonos
Copy link
Author

utkonos commented Mar 30, 2024

Should this be committed to the development branch?

@mrexodia
Copy link
Member

Yeah after some more testing it will be merged.

mrexodia added a commit that referenced this issue Apr 21, 2024
@mrexodia
Properly escape the command arguments for the WatchView
8b19bae 
Closes #3320
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug The issue describes a bug. It does not mean the bug has been reproduced by a developer.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mrexodia @utkonos