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.

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

Feature Request: Refresh Functionality #36

Open
i486 opened this issue May 18, 2024 · 0 comments
Open

Feature Request: Refresh Functionality #36

i486 opened this issue May 18, 2024 · 0 comments

Comments

@i486
Copy link

i486 commented May 18, 2024

Dear @rix0rrr

I am writing to suggest a feature enhancement for Windows Path Editor 1.7. Firstly, I would like to thank you for developing such a useful tool—it has significantly simplified the management of the PATH environment variable for me.

I have a feature request that I believe would further improve the usability of the tool. Currently, the tool does not update the displayed PATH variable when changes are made outside of the application, unless it is restarted. This can be somewhat inconvenient when managing the PATH variable frequently.

I would like to request the addition of a refresh functionality (F5 key) that allows users to update the displayed PATH variable without restarting the application. This feature would ensure that any changes made to the PATH variable externally (through the command line, other applications, or system settings) are immediately reflected within the Windows Path Editor.

Here are a few points detailing the proposed feature:

  • Functionality: Pressing F5 (or a dedicated refresh button) refreshes the current PATH variable displayed in the tool.
  • Purpose: To synchronize the PATH variable displayed in the tool with the current system environment variable.
  • Benefit: Enhances user experience by providing real-time updates and reducing the need to restart the application.

Thank you for considering this request. I believe this enhancement will be beneficial to many users.

Best regards,
i486

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant