-
Notifications
You must be signed in to change notification settings - Fork 99
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] Description column #9
Comments
Good suggestion that we will consider adding in the next version. |
The new version (v1.3.0) has been released, see if the new features get along well. |
Tried quickly (net 6 version). Seems to work fine. I see that you create the config.db file in Since netsh rules are system wide (and not per-user), you need to move the db file out of My mistake for suggesting I also suggest making the comment column 2x or 3x wider by default on the next release. You rarely want to put only 1 word in there ;-) Even better would be to remember window/columns size/positions between launches (make sure to check that it's not outside of visible screen), but I'll leave it up to you to create another feature request (or not) for this. |
The description and comment features are really nice; any way to automatically add 1 or both when doing a For example, I have a powershell script that auto deletes and creates new ports on bootup, with only the IP changing, and it would be really cool to persist those descriptions/comments. |
I created a fork and moved the |
Just a suggestion: it would be useful to add a column to add a name/description to each line.
You can't save/parse it directly with netsh command, but you could keep these in a separate file in
%localappdata%\PortProxyGUI
or something."If column values match this, then description = this."
When creating/editing a rule (or comment), update the file too.
The same file/code could even be used to add other features like disable/enable rule, export/import feature, etc.
It would probably not be perfect, but could definitely be useful when you end up with alot of rules.
The text was updated successfully, but these errors were encountered: