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

Configuration File #2643

Open
MyDrift-user opened this issue Aug 29, 2024 · 2 comments
Open

Configuration File #2643

MyDrift-user opened this issue Aug 29, 2024 · 2 comments

Comments

@MyDrift-user
Copy link
Contributor

Describe the solution you'd like

How about adding a configuration file for WinUtil, that will only be created/kept if a checkbox "keep personalisation" or smth in option list is checked.
Kinda adding the feature to erase any winutil leftovers or keep some stuff to have custom themes/configuration/other leftovers to make winutil loadup even faster.

@og-mrk
Copy link
Contributor

og-mrk commented Aug 29, 2024

Cool idea, the removal of leftovers (preferences, which currently there's none, and log files) is a plus IMO, as some people don't like bloating their system, or just want any future user to know you used WinUtil (.. for whatever reason), and it's possible to implement it without much hassle.

Cool suggestion @MyDrift-user

EDIT: Implementation wise for the GUI end is left to be discussed, I'll link this issue to #2226 GUI Tracking Issue for further assessment in the future.

@Marterich
Copy link
Contributor

Update: There actually are leftovers now. The theme and chocolatey settings are "saved" as a file under %localappdata%/winutil

It's still to be evaluated where and how we want to store persistent content in a manageable, centralized, standardized way. Ideas are Registry, config/ini file in localappdata

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

3 participants