Replies: 3 comments
-
This should be moved to https://github.com/valinet/ExplorerPatcher/discussions/categories/ideas |
Beta Was this translation helpful? Give feedback.
-
I thought we are supposed to use issues instead. If I have a choice between discussions and issues, I'll always choose issues, because they can be easily mentioned in commit messages, pull requests, other issues, and offer better tracking in general. Currently, there are no clear guidelines. |
Beta Was this translation helpful? Give feedback.
-
To me, issues are for bugs. New features go into ideas. If I'm wrong, please correct me. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Currently, there is no automated way to import the settings, and just importing the registry file is not enough in some cases.
When it gets implemented, users could easily automate the setup of ExplorerPatcher with a simple winget command:
winget install valinet.ExplorerPatcher --override "/import ExplorerPatcher_22621.1413.54.5.reg"
Alternatively, this could be a part of a separate binary, or ExplorerPatcher could just look for a .reg file in a specific location on startup.
Beta Was this translation helpful? Give feedback.
All reactions