[Bug 48312] New: Add a "Reset" button to the WINE Config UI.

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=48312

Bug ID: 48312
           Summary: Add a "Reset" button to the WINE Config UI.
           Product: Wine
           Version: 4.20
          Hardware: x86
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: -unknown
          Assignee: [e-mail]
          Reporter: [e-mail]
      Distribution: ---

Pressing the "Reset" button in the WINE Config UI would delete the current WINE
installation and create a new installation.

[Bug 48312] Add a "Reset" button to the WINE Config UI.

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=48312

Clinton H  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
       Distribution|---                         |Ubuntu
           Severity|normal                      |enhancement

[Bug 48312] Add a "Reset" button to the WINE Config UI.

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=48312

Clinton H  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
           Hardware|x86                         |x86-64

[Bug 48312] Add a "Reset" button to the WINE Config UI.

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=48312

--- Comment #1 from Nikolay Sivov  ---
One issue is that winecfg itself is running in prefix you're about to remove.
Various projects that help to maintain prefixes/wine builds are running as
regular applications, so it's not a problem there.
> From usability perspective this does not seem to be easier, you'll have to set

WINEPREFIX, then run winecfg in it just to remove it, as opposed to just
removing it.

[Bug 48312] Add a "Reset" button to the WINE Config UI.

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=48312

--- Comment #2 from Clinton H  ---
(In reply to Nikolay Sivov from comment #1)
> One issue is that winecfg itself is running in prefix you're about to
> remove. Various projects that help to maintain prefixes/wine builds are
> running as regular applications, so it's not a problem there.
>
> From usability perspective this does not seem to be easier, you'll have to
> set WINEPREFIX, then run winecfg in it just to remove it, as opposed to just
> removing it.

I meant to say, it would delete the windows installation(.wine folder) and then
create a new .wine folder.